CVE-2017-15090
First published: Tue Jan 23 2018(Updated: )
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.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| PowerDNS Recursor | >=4.0.0<=4.0.6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2017-15090?
CVE-2017-15090 is a vulnerability found in the DNSSEC validation component of PowerDNS Recursor.
What is the severity of CVE-2017-15090?
CVE-2017-15090 has a severity rating of medium (5.9).
How does CVE-2017-15090 affect PowerDNS Recursor?
CVE-2017-15090 allows an attacker in a man-in-the-middle position to accept signatures as valid even if the signed data is not in the DNSKEY's bailiwick.
Which versions of PowerDNS Recursor are affected by CVE-2017-15090?
PowerDNS Recursor versions 4.0.0 up to and including 4.0.6 are affected by CVE-2017-15090.
How can I fix CVE-2017-15090?
To fix CVE-2017-15090, update PowerDNS Recursor to version 4.0.7 or later.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- agent/references
- agent/remedy
- agent/author
- agent/weakness
- agent/severity
- agent/tags
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/first-publish-date
- agent/source
- vendor/powerdns
- canonical/powerdns recursor
- version/powerdns recursor/4.0.0
- version/powerdns recursor/4.0.6