Skip to content
Fencer Vulns
low 3.7

CVE-2018-1000003 json

Improper input validation bugs in DNSSEC validators components in PowerDNS version 4.1.0 allow attacker in man-in-the-middle position to de…

published 2018-01-22 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-1775

cvss
3.7
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
0
none known

Summary

Improper input validation bugs in DNSSEC validators components in PowerDNS version 4.1.0 allow attacker in man-in-the-middle position to deny existence of some data in DNS via packet replay.

Patch / fix

  • pdns-recursor Debian 14, Debian 13, Debian 12 4.1.1-1

debian advisories DEBIAN-CVE-2018-1000003

  • pdns-recursor openSUSE Tumbleweed 4.5.5-1.3
  • pdns-recursor Package Hub 12 SP1 4.1.2-5.1

opensuse advisories openSUSE-SU-2024:11157-1openSUSE-SU-2018:0953-1

  • pdns-recursor Alpine 3.24, Alpine 3.23, Alpine 3.22 +14 more 4.1.1-r0

alpine advisories ALPINE-CVE-2018-1000003

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-1000003 updated cvss 5.4

pdns: Improper validation of wildcard synthesized NSEC records

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.29% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 3.7 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.