Vulnerabilities (CVE)

Join the Common Vulnerabilities and Exposures (CVE) community and start to get notified about new vulnerabilities.

Filtered by vendor Nlnetlabs Subscribe
Filtered by product Ldns
Total 7 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2020-19861 1 Nlnetlabs 1 Ldns 2022-10-05 5.0 MEDIUM 7.5 HIGH
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. When the memcpy is copied, the 0xfe - ldns_rdf_size(salt_rdf) byte data can be copied, causing heap overflow information leakage.
CVE-2020-19860 1 Nlnetlabs 1 Ldns 2022-01-27 4.3 MEDIUM 6.5 MEDIUM
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. An attacker can leak information on the heap by constructing a zone file payload.
CVE-2017-1000232 1 Nlnetlabs 1 Ldns 2020-03-31 7.5 HIGH 9.8 CRITICAL
A double-free vulnerability in str2host.c in ldns 1.7.0 have unspecified impact and attack vectors.
CVE-2017-1000231 1 Nlnetlabs 1 Ldns 2018-02-03 7.5 HIGH 9.8 CRITICAL
A double-free vulnerability in parse.c in ldns 1.7.0 have unspecified impact and attack vectors.
CVE-2011-3581 1 Nlnetlabs 1 Ldns 2016-12-07 6.8 MEDIUM N/A
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.
CVE-2014-3209 1 Nlnetlabs 1 Ldns 2014-11-17 2.1 LOW N/A
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.
CVE-2009-1086 1 Nlnetlabs 1 Ldns 2009-05-14 6.4 MEDIUM N/A
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 record (RR) with a long (1) class field (clas variable) and possibly (2) TTL field.