NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
96 matching advisories · page 2 of 4Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2023-29583 yasm 1.3.0.55.g101bc was discovered to contain a stack overflow via the function parse_expr5 at /nasm/nasm-parse.c. yasm_project · yasm 2023-04-24 medium5.5 CVE-2023-29582 yasm 1.3.0.55.g101bc was discovered to contain a stack overflow via the function parse_expr1 at /nasm/nasm-parse.c. yasm_project · yasm 2023-04-24 medium5.5 CVE-2023-29581 yasm 1.3.0.55.g101bc has a segmentation violation in the function delete_Token at modules/preprocs/nasm/nasm-pp.c. yasm_project · yasm 2023-04-12 high7.8 CVE-2022-44370 NASM v2.16 was discovered to contain a heap buffer overflow in the component quote_for_pmake() asm/nasm.c:856 nasm · netwide_assembler 2023-03-29 medium5.5 CVE-2022-44369 NASM 2.16 (development) is vulnerable to 476: Null Pointer Dereference via output/outaout.c. nasm · netwide_assembler 2023-03-29 medium5.5 CVE-2022-44368 NASM v2.16 was discovered to contain a null pointer deference in the NASM component nasm · netwide_assembler 2023-03-29 medium5.5 CVE-2022-46457 NASM v2.16 was discovered to contain a segmentation violation in the component ieee_write_file at /output/outieee.c. nasm · netwide_assembler 2023-01-04 medium6.1 CVE-2022-46456 NASM v2.16 was discovered to contain a global buffer overflow in the component dbgdbg_typevalue at /output/outdbg.c. nasm · netwide_assembler 2023-01-04 medium5.5 CVE-2022-41420 nasm v2.16 was discovered to contain a stack overflow in the Ndisasm component nasm · netwide_assembler 2022-10-03 medium5.5 CVE-2021-33452 An issue was discovered in NASM version 2.16rc0. nasm · netwide_assembler 2022-07-26 medium5.5 CVE-2021-33450 An issue was discovered in NASM version 2.16rc0. nasm · netwide_assembler 2022-07-26 medium5.5 CVE-2021-45257 An infinite loop vulnerability exists in nasm 2.16rc0 via the gpaste_tokens function. nasm · netwide_assembler 2021-12-22 medium5.5 CVE-2021-45256 A Null Pointer Dereference vulnerability existfs in nasm 2.16rc0 via asm/preproc.c. nasm · netwide_assembler 2021-12-22 low3.3 CVE-2020-18974 Buffer Overflow in Netwide Assembler (NASM) v2.15.xx allows attackers to cause a denial of service via 'crc64i' in the component 'nasmlib/crc64'. nasm · netwide_assembler 2021-08-25 critical9.8 CVE-2020-24978 In NASM 2.15.04rc3, there is a double-free vulnerability in pp_tokline asm/preproc.c. nasm · netwide_assembler 2020-09-04 medium5.5 CVE-2020-24242 In Netwide Assembler (NASM) 2.15rc10, SEGV can be triggered in tok_text in asm/preproc.c by accessing READ memory. nasm · netwide_assembler 2020-08-25 medium5.5 CVE-2020-24241 In Netwide Assembler (NASM) 2.15rc10, there is heap use-after-free in saa_wbytes in nasmlib/saa.c. nasm · netwide_assembler 2020-08-25 high7.1 CVE-2019-20352 In Netwide Assembler (NASM) 2.15rc0, a heap-based buffer over-read occurs (via a crafted .asm file) in set_text_free when called from expand_one_smacro in asm/… nasm · netwide_assembler 2020-01-06 medium5.5 CVE-2019-20334 In Netwide Assembler (NASM) 2.14.02, stack consumption occurs in expr# functions in asm/eval.c. nasm · netwide_assembler 2020-01-04 medium5.5 CVE-2019-14248 In libnasm.a in Netwide Assembler (NASM) 2.14.xx, asm/pragma.c allows a NULL pointer dereference in process_pragma, search_pragma_list, and nasm_set_limit when… nasm · netwide_assembler 2019-07-24 high7.8 CVE-2019-8343 In Netwide Assembler (NASM) 2.14.02, there is a use-after-free in paste_tokens in asm/preproc.c. nasm · netwide_assembler 2019-02-15 medium5.5 CVE-2019-7147 A buffer over-read exists in the function crc64ib in crc64.c in nasmlib in Netwide Assembler (NASM) 2.14rc16. nasm · netwide_assembler 2019-01-29 medium5.5 CVE-2019-6291 An issue was discovered in the function expr6 in eval.c in Netwide Assembler (NASM) through 2.14.02. nasm · netwide_assembler 2019-01-15 medium5.5 CVE-2019-6290 An infinite recursion issue was discovered in eval.c in Netwide Assembler (NASM) through 2.14.02. nasm · netwide_assembler 2019-01-15 medium5.5 CVE-2018-20538 There is a use-after-free at asm/preproc.c (function pp_getline) in Netwide Assembler (NASM) 2.14rc16 that will cause a denial of service during certain finish… nasm · netwide_assembler 2018-12-28 medium5.5 CVE-2018-20535 There is a use-after-free at asm/preproc.c (function pp_getline) in Netwide Assembler (NASM) 2.14rc16 that will cause a denial of service during a line-number … nasm · netwide_assembler 2018-12-28 medium5.5 CVE-2018-1000886 nasm version 2.14.01rc5, 2.15 contains a Buffer Overflow vulnerability in asm/stdscan.c:130 that can result in Stack-overflow caused by triggering endless macr… nasm · netwide_assembler 2018-12-20 medium5.5 CVE-2018-19755 There is an illegal address access at asm/preproc.c (function: is_mmacro) in Netwide Assembler (NASM) 2.14rc16 that will cause a denial of service (out-of-boun… nasm · netwide_assembler 2018-11-30 high7.8 CVE-2018-19216 Netwide Assembler (NASM) before 2.13.02 has a use-after-free in detoken at asm/preproc.c. nasm · netwide_assembler, debian · debian_linux 2018-11-12 high7.8 CVE-2018-19215 Netwide Assembler (NASM) 2.14rc16 has a heap-based buffer over-read in expand_mmac_params in asm/preproc.c for the special cases of the % and $ and ! nasm · netwide_assembler, redhat · enterprise_linux 2018-11-12

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.