VDB

CVE-2017-15090

CVE-2017-15090 PUBLISHED

Reported by redhat · Published January 23, 2018

An issue has been found in the DNSSEC validation component of PowerDNS Recursor from 4.0.0 and up to and including 4.0.6, where the signatures might have been accepted as valid even if the signed data was not in bailiwick of the DNSKEY used to sign it. This allows an attacker in position of man-in-the-middle to alter the content of records by issuing a valid signature for the crafted records.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
recursorpowerdns4.0.6

Affected products

VendorProductVersions
PowerDNSPowerDNSfrom 4.0.0 and up to and including 4.0.6
PowerDNSPowerDNS4.0.0
archpowerdns-recursor0
alpinepdns-recursor0

Timeline

  • Jan 23, 2018 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Sep 8, 2025 CVE Updated
  • Jun 1, 2026 Security Advisory
  • Oct 2, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2017-15090
vulnetix vdb fixes CVE-2017-15090

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-15090/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

  • x_refsource_CONFIRM
  • 101982 vdb-entryx_refsource_BID
Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›