CVE-2017-15092
published 2018-01-23CVE-2017-15092: A cross-site scripting issue has been found in the web interface of PowerDNS Recursor from 4.0.0 up to and including 4.0.6, where the qname of DNS queries was…
PriorityP427medium6.1CVSS 3.0
AVNACLPRNUIRSCCLILAN
EPSS
2.32%
81.3th percentile
A cross-site scripting issue has been found in the web interface of PowerDNS Recursor from 4.0.0 up to and including 4.0.6, where the qname of DNS queries was displayed without any escaping, allowing a remote attacker to inject HTML and Javascript code into the web interface, altering the content.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | pdns-recursor | < pdns-recursor 4.0.7-1 (bookworm) | pdns-recursor 4.0.7-1 (bookworm) |
| powerdns | powerdns_recursor | — | — |
| powerdns | recursor | 4.0.0 – 4.0.6 | — |
CVSS provenance
nvdv3.06.1MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:P/A:N
osv6.1MEDIUM
vendor_debian6.1MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Debian
CVE-2017-15092: pdns-recursor - A cross-site scripting issue has been found in the web interface of PowerDNS Rec...
vendor_debian·2017·CVSS 6.1
CVE-2017-15092 [MEDIUM] CVE-2017-15092: pdns-recursor - A cross-site scripting issue has been found in the web interface of PowerDNS Rec...
A cross-site scripting issue has been found in the web interface of PowerDNS Recursor from 4.0.0 up to and including 4.0.6, where the qname of DNS queries was displayed without any escaping, allowing a remote attacker to inject HTML and Javascript code into the web interface, altering the content.
Scope: local
bookworm: resolved (fixed in 4.0.7-1)
bullseye: resolved (fixed in 4.0.7-1)
forky: resolved (fixed in 4.0.7-1)
sid: resolved (fixed in 4.0.7-1)
trixie: resolved (fixed in 4.0.7-1)
GHSA
GHSA-5v6v-h944-2g93: A cross-site scripting issue has been found in the web interface of PowerDNS Recursor from 4
ghsa_unreviewed·2022-05-13
CVE-2017-15092 [MEDIUM] CWE-79 GHSA-5v6v-h944-2g93: A cross-site scripting issue has been found in the web interface of PowerDNS Recursor from 4
A cross-site scripting issue has been found in the web interface of PowerDNS Recursor from 4.0.0 up to and including 4.0.6, where the qname of DNS queries was displayed without any escaping, allowing a remote attacker to inject HTML and Javascript code into the web interface, altering the content.
OSV
CVE-2017-15092: A cross-site scripting issue has been found in the web interface of PowerDNS Recursor from 4
osv·2018-01-23·CVSS 6.1
CVE-2017-15092 [MEDIUM] CVE-2017-15092: A cross-site scripting issue has been found in the web interface of PowerDNS Recursor from 4
A cross-site scripting issue has been found in the web interface of PowerDNS Recursor from 4.0.0 up to and including 4.0.6, where the qname of DNS queries was displayed without any escaping, allowing a remote attacker to inject HTML and Javascript code into the web interface, altering the content.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2017-15090 CVE-2017-15092 CVE-2017-15093 CVE-2017-15094 CVE-2017-15120 pdns-recursor: various flaws [epel-all]
bugzilla·2017-12-11·CVSS 5.9
CVE-2017-15090 [MEDIUM] CVE-2017-15090 CVE-2017-15092 CVE-2017-15093 CVE-2017-15094 CVE-2017-15120 pdns-recursor: various flaws [epel-all]
CVE-2017-15090 CVE-2017-15092 CVE-2017-15093 CVE-2017-15094 CVE-2017-15120 pdns-recursor: various flaws [epel-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue
Bugzilla
CVE-2017-15090 CVE-2017-15092 CVE-2017-15093 CVE-2017-15094 pdns-recursor: 4.0.7 release fixing security issues
bugzilla·2017-12-11·CVSS 5.9
CVE-2017-15090 [MEDIUM] CVE-2017-15090 CVE-2017-15092 CVE-2017-15093 CVE-2017-15094 pdns-recursor: 4.0.7 release fixing security issues
CVE-2017-15090 CVE-2017-15092 CVE-2017-15093 CVE-2017-15094 pdns-recursor: 4.0.7 release fixing security issues
CVE-2017-15090
An issue has been found in the DNSSEC validation component of PowerDNS Recursor, 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. This issue has been assigned CVE-2017-15090.
https://doc.powerdns.com/recursor/security-advisories/powerdns-advisory-2017-03.html
CVE-2017-15092
An issue has been found in the web interface of PowerDNS Recursor, where the qname of DNS queries was displayed without any escaping, allowing a remote attacker to inje
Fortinet
PowerDNS Recursor HTML/Script Injection Vulnerability – A Walkthrough
blogs_fortinet·2017-12-02·CVSS 6.1
[MEDIUM] PowerDNS Recursor HTML/Script Injection Vulnerability – A Walkthrough
FORTIGUARD LABS THREAT RESEARCH
PowerDNS Recursor HTML/Script Injection Vulnerability – A Walkthrough
By Chris Navarrete | December 02, 2017
PowerDNS Recursor is a high-end, high-performance resolving name server that powers the DNS resolution of at least a hundred million subscribers. The “Recursor” is one of two name server products whose primary goal is to act as resolving DNS server.
On Aug. 7, 2017, I reported an XSS (cross-site scripting) vulnerability to PowerDNS and its Security Team. They assigned it the identifier CVE-2017-15092.
In this report I will explain how I was able to identify and trigger the vulnerability.
Identifying the Attack Vector
As part of FortiGuard Labs’ regular zero-day research efforts, I decided to start with a Black-box approach to see if I could iden
2018-01-23
Published