NetSight

Security Dashboard

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

Reset
185 matching advisories · page 4 of 7Index updated 10 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2022-1283 NULL Pointer Dereference in r_bin_ne_get_entrypoints function in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-08 high7.8 CVE-2022-1240 Heap buffer overflow in libr/bin/format/mach0/mach0.c in GitHub repository radareorg/radare2 prior to 5.8.6. radare · radare2 2022-04-06 high7.8 CVE-2022-1238 Out-of-bounds Write in libr/bin/format/ne/ne.c in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-06 high7.8 CVE-2022-1237 Improper Validation of Array Index in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-06 medium5.5 CVE-2022-1244 heap-buffer-overflow in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-05 medium6.6 CVE-2022-1207 Out-of-bounds read in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-04-01 medium5.5 CVE-2022-1052 Heap Buffer Overflow in iterate_chained_fixups in GitHub repository radareorg/radare2 prior to 5.6.6. radare · radare2 2022-03-24 high7.5 CVE-2022-1061 Heap Buffer Overflow in parseDragons in GitHub repository radareorg/radare2 prior to 5.6.8. radare · radare2 2022-03-24 high7.8 CVE-2022-1031 Use After Free in op_is_set_bp in GitHub repository radareorg/radare2 prior to 5.6.6. radare · radare2 2022-03-22 medium5.5 CVE-2022-0849 Use After Free in r_reg_get_name_idx in GitHub repository radareorg/radare2 prior to 5.6.6. radare · radare2 2022-03-05 high7.5 CVE-2021-4021 A vulnerability was found in Radare2 in versions prior to 5.6.2, 5.6.0, 5.5.4 and 5.5.2. radare · radare2 2022-02-24 medium5.5 CVE-2022-0695 Denial of Service in GitHub repository radareorg/radare2 prior to 5.6.4. radare · radare2, fedoraproject · fedora 2022-02-24 medium5.5 CVE-2022-0476 Denial of Service in GitHub repository radareorg/radare2 prior to 5.6.4. radare · radare2, fedoraproject · fedora 2022-02-23 high7.1 CVE-2022-0713 Heap-based Buffer Overflow in GitHub repository radareorg/radare2 prior to 5.6.4. radare · radare2, fedoraproject · fedora 2022-02-22 medium5.5 CVE-2022-0712 NULL Pointer Dereference in GitHub repository radareorg/radare2 prior to 5.6.4. radare · radare2, fedoraproject · fedora 2022-02-22 high7.8 CVE-2022-0676 Heap-based Buffer Overflow in GitHub repository radareorg/radare2 prior to 5.6.4. radare · radare2, fedoraproject · fedora 2022-02-22 critical9.8 CVE-2022-0559 Use After Free in GitHub repository radareorg/radare2 prior to 5.6.2. radare · radare2, fedoraproject · fedora 2022-02-16 high7.8 CVE-2022-0523 Use After Free in GitHub repository radareorg/radare2 prior to 5.6.2. radare · radare2, fedoraproject · fedora 2022-02-08 high7.1 CVE-2022-0522 Access of Memory Location Before Start of Buffer in NPM radare2.js prior to 5.6.2. radare · radare2, fedoraproject · fedora 2022-02-08 high7.1 CVE-2022-0521 Access of Memory Location After End of Buffer in GitHub repository radareorg/radare2 prior to 5.6.2. radare · radare2, fedoraproject · fedora 2022-02-08 high7.8 CVE-2022-0520 Use After Free in NPM radare2.js prior to 5.6.2. radare · radare2, fedoraproject · fedora 2022-02-08 high7.1 CVE-2022-0519 Buffer Access with Incorrect Length Value in GitHub repository radareorg/radare2 prior to 5.6.2. radare · radare2, fedoraproject · fedora 2022-02-08 high7.1 CVE-2022-0518 Heap-based Buffer Overflow in GitHub repository radareorg/radare2 prior to 5.6.2. radare · radare2, fedoraproject · fedora 2022-02-08 critical9.8 CVE-2022-0139 Use After Free in GitHub repository radareorg/radare2 prior to 5.6.0. radare · radare2 2022-02-08 medium5.5 CVE-2022-0419 NULL Pointer Dereference in GitHub repository radareorg/radare2 prior to 5.6.0. radare · radare2, fedoraproject · fedora 2022-02-01 medium5.5 CVE-2022-0173 radare2 is vulnerable to Out-of-bounds Read radare · radare2, fedoraproject · fedora 2022-01-11 high7.5 CVE-2021-3673 A vulnerability was found in Radare2 in version 5.3.1. radare · radare2, fedoraproject · fedora 2021-08-02 critical9.8 CVE-2020-24133 A heap buffer overflow vulnerability in the r_asm_swf_disass function of Radare2-extras before commit e74a93c allows attackers to execute arbitrary code or car… radare · radare2-extras 2021-07-14 medium5.5 CVE-2021-32613 In radare2 through 5.3.0 there is a double free vulnerability in the pyc parse via a crafted file which can lead to DoS. radare · radare2, fedoraproject · fedora 2021-05-14 high7.5 CVE-2020-17487 radare2 4.5.0 misparses signature information in PE files, causing a segmentation fault in r_x509_parse_algorithmidentifier in libr/util/x509.c. radare · radare2, fedoraproject · fedora 2020-08-11

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.