VDB

CVE-2017-15091

CVE-2017-15091 PUBLISHED

Reported by redhat · Published January 23, 2018

An issue has been found in the API component of PowerDNS Authoritative 4.x up to and including 4.0.4 and 3.x up to and including 3.4.11, where some operations that have an impact on the state of the server are still allowed even though the API has been configured as read-only via the api-readonly keyword. This missing check allows an attacker with valid API credentials to flush the cache, trigger a zone transfer or send a NOTIFY.

Fixed versions

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

PackageEcosystemFixed in
pdnsAlpine4.0.5-r0
powerdnsArch Linux4.0.5-1
authoritativepowerdns4.0.4, 3.4.11

Affected products

VendorProductVersions
PowerDNSPowerDNS Authoritative4.x up to and including 4.0.4, 3.x up to and including 3.4.11
alpinepdns0
archpowerdns0
PowerDNSPowerDNS Authoritative4.0.4, 3.4.11

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-15091
vulnetix vdb fixes CVE-2017-15091

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-15091/fixes/registry"

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

References

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