Unbound vulnerabilitiesRanked by how likely they are to be used.
Unbound is made by Nlnetlabs. We track 30 published vulnerabilities in it, across 109 versions. None of them is on the list of flaws known to be exploited today. If you run Unbound, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Unbound vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Unbound's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Unbound flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%CVE-2023-50387High
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue.
- 32%CVE-2014-8602Medium
iterator.c in NLnet Labs Unbound before 1.5.1 does not limit delegation chaining, which allows remote attackers to cause a denial of service (memory and CPU consumption) via a large or infinite number of referrals.
- 7.1%CVE-2011-1922Medium
daemon/worker.c in Unbound 1.x before 1.4.10, when debugging functionality and the interface-automatic option are enabled, allows remote attackers to cause a denial of service (assertion failure and daemon exit) via...
- 3.6%CVE-2020-12663High
Unbound before 1.10.1 has an infinite loop via malformed DNS answers received from upstream servers.
- 3.5%CVE-2019-16866High
Unbound before 1.9.4 accesses uninitialized memory, which allows remote attackers to trigger a crash via a crafted NOTIFY query.
- 3.2%CVE-2020-12662High
Unbound before 1.10.1 has Insufficient Control of Network Message Volume, aka an "NXNSAttack" issue.
- 3.2%CVE-2019-18934High
Unbound 1.6.4 through 1.9.4 contain a vulnerability in the ipsec module that can cause shell code execution after receiving a specially crafted answer.
- 3.2%CVE-2017-15105Medium
A flaw was found in the way unbound before 1.6.8 validated wildcard-synthesized NSEC records.
- 3.0%CVE-2009-3602High
Unbound before 1.3.4 does not properly verify signatures for NSEC3 records, which allows remote attackers to cause secure delegations to be downgraded via DNS spoofing or other DNS-related attacks in conjunction with...
- 2.9%CVE-2019-25035Critical
Unbound before 1.9.5 allows an out-of-bounds write in sldns_bget_token_par.
Running Unbound? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Certain DNSSEC aspects of the DNS protocol (in RFC 4033, 4034, 4035, 6840, and related RFCs) allow remote attackers to cause a denial of service (CPU consumption) via one or more DNSSEC responses, aka the "KeyTrap" issue. One of the concerns is that, when there is a zone with many DNSKEY and RRSIG records, the protocol specification implies that an algorithm must evaluate all combinations of DNSKEY and RRSIG records.
- Matched to
- Unbound on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 30 published vulnerabilities listed under the name Unbound, across 109 versions.
None of Unbound's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Unbound. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.