PowerDNS Recursor up to 4.0.6 DNSSEC Validator signature verification

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.5$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in PowerDNS Recursor up to 4.0.6. Affected is an unknown function of the component DNSSEC Validator. The manipulation leads to signature verification. This vulnerability is documented as CVE-2017-15090. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in PowerDNS Recursor up to 4.0.6 (Domain Name Software). This issue affects some unknown functionality of the component DNSSEC Validator. The manipulation with an unknown input leads to a signature verification vulnerability. Using CWE to declare the problem leads to CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The bug was discovered 11/27/2017. The weakness was released 01/23/2018 with FortiGuard Labs (Website). It is possible to read the advisory at doc.powerdns.com. The identification of this vulnerability is CVE-2017-15090 since 10/08/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available.

The vulnerability was handled as a non-public zero-day exploit for at least 15 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 105198 (Fedora 26 : pdns-recursor (2017-1585789772)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 277398 (Fedora Security Update for pdns-recursor (FEDORA-2018-76c82b393e)).

Upgrading eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (105198) and SecurityFocus (BID 101982†). Entries connected to this vulnerability are available at VDB-112287, VDB-112334, VDB-112332 and VDB-112333. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.6
VulDB Meta Temp Score: 6.5

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.9
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Signature verification
CWE: CWE-347 / CWE-345
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 105198
Nessus Name: Fedora 26 : pdns-recursor (2017-1585789772)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 800644
OpenVAS Name: PowerDNS Recursor Multiple Vulnerabilities
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

10/08/2017 🔍
11/27/2017 +50 days 🔍
11/27/2017 +0 days 🔍
12/12/2017 +15 days 🔍
12/13/2017 +1 days 🔍
01/23/2018 +41 days 🔍
01/23/2018 +0 days 🔍
01/24/2018 +1 days 🔍
02/02/2023 +1835 days 🔍

Sourcesinfo

Advisory: FEDORA-2017-1585789772
Researcher: everyman, Kees Monshouwer, Nixu, Chris Navarrete
Organization: FortiGuard Labs
Status: Not defined
Confirmation: 🔍

CVE: CVE-2017-15090 (🔍)
GCVE (CVE): GCVE-0-2017-15090
GCVE (VulDB): GCVE-100-112331
SecurityFocus: 101982 - PowerDNS Authoritative Server Module Multiple Security Vulnerabilities

See also: 🔍

Entryinfo

Created: 01/24/2018 07:58
Updated: 02/02/2023 12:54
Changes: 01/24/2018 07:58 (74), 12/27/2019 06:25 (7), 02/01/2021 14:17 (2), 02/02/2023 12:54 (3)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!