NetSight

Security Dashboard

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

Reset
185 matching advisories · page 3 of 7Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2022-28069 A heap buffer overflow in vax_opfunction in radare2 5.4.2 and 5.4.0. radare · radare2 2023-08-22 high7.5 CVE-2022-28068 A heap buffer overflow in r_sleb128 function in radare2 5.4.2 and 5.4.0. radare · radare2 2023-08-22 critical9.8 CVE-2023-4322 Heap-based Buffer Overflow in GitHub repository radareorg/radare2 prior to 5.9.0. radare · radare2, fedoraproject · fedora 2023-08-14 critical10.0 CVE-2021-32495 Radare2 has a use-after-free vulnerability in pyc parser's get_none_object function. radare · radare2 2023-07-07 critical10.0 CVE-2021-32494 Radare2 has a division by zero vulnerability in Mach-O parser's rebase_buffer function. radare · radare2 2023-07-07 high7.5 CVE-2023-1605 Denial of Service in GitHub repository radareorg/radare2 prior to 5.8.6. radare · radare2 2023-03-23 medium5.5 CVE-2023-27114 radare2 v5.8.3 was discovered to contain a segmentation fault via the component wasm_dis at p/wasm/wasm.c. radare · radare2 2023-03-10 high7.8 CVE-2023-0302 Failure to Sanitize Special Elements into a Different Plane (Special Element Injection) in GitHub repository radareorg/radare2 prior to 5.8.2. radare · radare2 2023-01-15 high7.5 CVE-2022-4843 NULL Pointer Dereference in GitHub repository radareorg/radare2 prior to 5.8.2. radare · radare2 2022-12-29 high7.8 CVE-2022-4398 Integer Overflow or Wraparound in GitHub repository radareorg/radare2 prior to 5.8.0. radare · radare2 2022-12-10 high7.5 CVE-2020-27795 A segmentation fault was discovered in radare2 with adf command. radare · radare2 2022-08-19 critical9.1 CVE-2020-27794 A double free issue was discovered in radare2 in cmd_info.c:cmd_info(). radare · radare2 2022-08-19 high7.5 CVE-2020-27793 An off-by-one overflow flaw was found in radare2 due to mismatched array length in core_java.c. radare · radare2 2022-08-19 medium5.5 CVE-2022-34520 Radare2 v5.7.2 was discovered to contain a NULL pointer dereference via the function r_bin_file_xtr_load_buffer at bin/bfile.c. radare · radare2 2022-07-22 medium5.5 CVE-2022-34502 Radare2 v5.7.0 was discovered to contain a heap buffer overflow via the function consume_encoded_name_new at format/wasm/wasm.c. radare · radare2 2022-07-22 critical9.1 CVE-2022-1899 Out-of-bounds Read in GitHub repository radareorg/radare2 prior to 5.7.0. radare · radare2 2022-05-26 medium5.5 CVE-2021-44974 radareorg radare2 version 5.5.2 is vulnerable to NULL Pointer Dereference via libr/bin/p/bin_symbols.c binary symbol parser. radare · radare2 2022-05-25 medium5.5 CVE-2021-44975 radareorg radare2 5.5.2 is vulnerable to Buffer Overflow via /libr/core/anal_objc.c mach-o parser. radare · radare2 2022-05-24 high7.8 CVE-2022-1809 Access of Uninitialized Pointer in GitHub repository radareorg/radare2 prior to 5.7.0. radare · radare2 2022-05-21 high7.1 CVE-2022-1714 Out-of-bounds Read in GitHub repository radareorg/radare2 prior to 5.7.0. radare · radare2 2022-05-13 medium5.5 CVE-2022-1649 Null pointer dereference in libr/bin/format/mach0/mach0.c in radareorg/radare2 in GitHub repository radareorg/radare2 prior to 5.7.0. radare · radare2 2022-05-10 high7.1 CVE-2022-1452 Out-of-bounds Read in r_bin_java_bootstrap_methods_attr_new function in GitHub repository radareorg/radare2 prior to 5.7.0. radare · radare2 2022-04-24 high7.1 CVE-2022-1451 Out-of-bounds Read in r_bin_java_constant_value_attr_new function in GitHub repository radareorg/radare2 prior to 5.7.0. radare · radare2 2022-04-24 medium5.5 CVE-2022-1444 heap-use-after-free in GitHub repository radareorg/radare2 prior to 5.7.0. radare · radare2 2022-04-23 high7.1 CVE-2022-1437 Heap-based Buffer Overflow in GitHub repository radareorg/radare2 prior to 5.7.0. radare · radare2 2022-04-22 medium6.1 CVE-2022-1383 Heap-based Buffer Overflow in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-18 medium5.5 CVE-2022-1382 NULL Pointer Dereference in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-18 critical9.1 CVE-2022-1297 Out-of-bounds Read in r_bin_ne_get_entrypoints function in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-11 critical9.1 CVE-2022-1296 Out-of-bounds read in `r_bin_ne_get_relocs` function in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-11 medium5.5 CVE-2022-1284 heap-use-after-free in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-08

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.