CVE-2017-15091
Published: 23 January 2018
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.
Priority
Status
Package | Release | Status |
---|---|---|
pdns Launchpad, Ubuntu, Debian |
artful |
Ignored
(end of life)
|
bionic |
Not vulnerable
(4.1.1-1)
|
|
cosmic |
Not vulnerable
(4.1.1-1)
|
|
disco |
Not vulnerable
(4.1.1-1)
|
|
eoan |
Not vulnerable
(4.1.1-1)
|
|
focal |
Not vulnerable
(4.1.1-1)
|
|
groovy |
Not vulnerable
(4.1.1-1)
|
|
hirsute |
Not vulnerable
(4.1.1-1)
|
|
impish |
Not vulnerable
(4.1.1-1)
|
|
jammy |
Not vulnerable
(4.1.1-1)
|
|
kinetic |
Not vulnerable
(4.1.1-1)
|
|
lunar |
Not vulnerable
(4.1.1-1)
|
|
mantic |
Not vulnerable
(4.1.1-1)
|
|
noble |
Not vulnerable
(4.1.1-1)
|
|
trusty |
Does not exist
(trusty was needed)
|
|
upstream |
Released
(4.0.5-1)
|
|
xenial |
Needed
|
|
zesty |
Ignored
(end of life)
|
Severity score breakdown
Parameter | Value |
---|---|
Base score | 7.1 |
Attack vector | Network |
Attack complexity | Low |
Privileges required | Low |
User interaction | None |
Scope | Unchanged |
Confidentiality | None |
Integrity impact | Low |
Availability impact | High |
Vector | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H |