NetSight

Security Dashboard

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

Reset
108 matching advisories · page 3 of 4Index updated 4 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2023-39915 NLnet Labs' Routinator up to and including version 0.12.1 may crash when trying to parse certain malformed RPKI objects. nlnetlabs · routinator 2023-09-13 high7.5 CVE-2023-39914 BER/CER/DER decoder panics on invalid input rust · bcder 2023-09-13 high7.5 CVE-2023-0158 NLnet Labs Krill supports direct access to the RRDP repository content through its built-in web server at the "/rrdp" endpoint. nlnetlabs · krill 2023-01-17 high7.5 CVE-2022-3204 A vulnerability named 'Non-Responsive Delegation Attack' (NRDelegation Attack) has been discovered in various DNS resolving software. nlnetlabs · unbound, fedoraproject · fedora 2022-09-26 high7.5 CVE-2022-3029 NLnet Labs Routinator has Reachable Assertion vulnerability rust · routinator 2022-09-13 medium6.5 CVE-2022-30699 NLnet Labs Unbound, up to and including version 1.16.1, is vulnerable to a novel type of the "ghost domain names" attack. nlnetlabs · unbound, fedoraproject · fedora 2022-08-01 medium6.5 CVE-2022-30698 NLnet Labs Unbound, up to and including version 1.16.1 is vulnerable to a novel type of the "ghost domain names" attack. nlnetlabs · unbound, fedoraproject · fedora 2022-08-01 high7.5 CVE-2020-19861 When a zone file in ldns 1.7.1 is parsed, the function ldns_nsec3_salt_data is too trusted for the length value obtained from the zone file. nlnetlabs · ldns 2022-01-21 medium6.5 CVE-2020-19860 When ldns version 1.7.1 verifies a zone file, the ldns_rr_new_frm_str_internal function has a heap out of bounds read vulnerability. nlnetlabs · ldns 2022-01-21 high7.5 CVE-2021-43174 Memory exhaustion in routinator rust · routinator 2021-11-09 high7.5 CVE-2021-43173 In NLnet Labs Routinator prior to 0.10.2, a validation run can be delayed significantly by an RRDP repository by not answering but slowly drip-feeding bytes to… nlnetlabs · routinator, debian · debian_linux 2021-11-09 high7.5 CVE-2021-43172 Routinator infinite loop vulnerability rust · routinator 2021-11-09 high7.5 CVE-2021-41531 NLnet Labs Routinator prior to 0.10.0 produces invalid RTR payload if an RPKI CA uses too large values in the max-length parameter in a ROA. nlnetlabs · routinator 2021-09-21 critical9.8 CVE-2019-25042 Unbound before 1.9.5 allows an out-of-bounds write via a compressed name in rdata_copy. nlnetlabs · unbound, debian · debian_linux 2021-04-27 high7.5 CVE-2019-25041 Unbound before 1.9.5 allows an assertion failure via a compressed name in dname_pkt_copy. nlnetlabs · unbound, debian · debian_linux 2021-04-27 high7.5 CVE-2019-25040 Unbound before 1.9.5 allows an infinite loop via a compressed name in dname_pkt_copy. nlnetlabs · unbound, debian · debian_linux 2021-04-27 critical9.8 CVE-2019-25039 Unbound before 1.9.5 allows an integer overflow in a size calculation in respip/respip.c. nlnetlabs · unbound, debian · debian_linux 2021-04-27 critical9.8 CVE-2019-25038 Unbound before 1.9.5 allows an integer overflow in a size calculation in dnscrypt/dnscrypt.c. nlnetlabs · unbound, debian · debian_linux 2021-04-27 high7.5 CVE-2019-25037 Unbound before 1.9.5 allows an assertion failure and denial of service in dname_pkt_copy via an invalid packet. nlnetlabs · unbound, debian · debian_linux 2021-04-27 high7.5 CVE-2019-25036 Unbound before 1.9.5 allows an assertion failure and denial of service in synth_cname. nlnetlabs · unbound, debian · debian_linux 2021-04-27 critical9.8 CVE-2019-25035 Unbound before 1.9.5 allows an out-of-bounds write in sldns_bget_token_par. nlnetlabs · unbound, debian · debian_linux 2021-04-27 critical9.8 CVE-2019-25034 Unbound before 1.9.5 allows an integer overflow in sldns_str2wire_dname_buf_origin, leading to an out-of-bounds write. nlnetlabs · unbound, debian · debian_linux 2021-04-27 critical9.8 CVE-2019-25033 Unbound before 1.9.5 allows an integer overflow in the regional allocator via the ALIGN_UP macro. nlnetlabs · unbound, debian · debian_linux 2021-04-27 critical9.8 CVE-2019-25032 Unbound before 1.9.5 allows an integer overflow in the regional allocator via regional_alloc. nlnetlabs · unbound, debian · debian_linux 2021-04-27 medium5.9 CVE-2019-25031 Unbound before 1.9.5 allows configuration injection in create_unbound_ad_servers.sh upon a successful man-in-the-middle attack against a cleartext HTTP session. nlnetlabs · unbound, debian · debian_linux 2021-04-27 medium5.5 CVE-2020-28935 NLnet Labs Unbound, up to and including version 1.12.0, and NLnet Labs NSD, up to and including version 4.3.3, contain a local vulnerability that would allow f… nlnetlabs · name_server_daemon, nlnetlabs · unbound, debian · debian_linux 2020-12-07 high7.5 CVE-2020-10772 An incomplete fix for CVE-2020-12662 was shipped for Unbound in Red Hat Enterprise Linux 7, as part of erratum RHSA-2020:2414. nlnetlabs · unbound 2020-11-27 high7.4 CVE-2020-17366 An issue was discovered in NLnet Labs Routinator 0.1.0 through 0.7.1. nlnetlabs · routinator 2020-08-05 high7.5 CVE-2020-12663 Unbound before 1.10.1 has an infinite loop via malformed DNS answers received from upstream servers. nlnetlabs · unbound, debian · debian_linux, opensuse · leap +2 2020-05-19 high7.5 CVE-2020-12662 Unbound before 1.10.1 has Insufficient Control of Network Message Volume, aka an "NXNSAttack" issue. nlnetlabs · unbound, debian · debian_linux, opensuse · leap +2 2020-05-19

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.