Ldns vulnerabilitiesRanked by how likely they are to be used.
Ldns is made by Nlnetlabs. We track 7 published vulnerabilities in it, across 35 versions. None of them is on the list of flaws known to be exploited today. If you run Ldns, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Ldns vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Ldns's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Ldns 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.
- 4.1%CVE-2011-3581Medium
Heap-based buffer overflow in the ldns_rr_new_frm_str_internal function in ldns before 1.6.11 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a Resource Record...
- 3.5%CVE-2009-1086Medium
Heap-based buffer overflow in the ldns_rr_new_frm_str_internal function in ldns 1.4.x allows remote attackers to cause a denial of service (memory corruption) and possibly execute arbitrary code via a DNS resource...
- 2.7%CVE-2017-1000231Critical
A double-free vulnerability in parse.c in ldns 1.7.0 have unspecified impact and attack vectors.
- 2.3%CVE-2017-1000232Critical
A double-free vulnerability in str2host.c in ldns 1.7.0 have unspecified impact and attack vectors.
- 1.5%CVE-2020-19861High
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.
- 1.3%CVE-2020-19860Medium
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.
- 0.4%
The ldns-keygen tool in ldns 1.6.x uses the current umask to set the privileges of the private key, which might allow local users to obtain the private key by reading the file.
Running Ldns? 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
Heap-based buffer overflow in the ldns_rr_new_frm_str_internal function in ldns before 1.6.11 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a Resource Record (RR) with an unknown type containing input that is longer than a specified length.
- Matched to
- Ldns 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 7 published vulnerabilities listed under the name Ldns, across 35 versions.
None of Ldns's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Ldns. 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.