Skip to content

miekg/dns parsing error leads to nil pointer dereference and DoS

High severity GitHub Reviewed Published May 18, 2021 to the GitHub Advisory Database • Updated May 20, 2024

Package

gomod github.com/miekg/dns (Go)

Affected versions

< 1.0.10

Patched versions

1.0.10

Description

An issue was discovered in setTA in scan_rr.go in the Miek Gieben DNS library before 1.0.10 for Go. A dns.ParseZone() parsing error causes a segmentation violation, leading to denial of service.

References

Reviewed May 11, 2021
Published to the GitHub Advisory Database May 18, 2021
Last updated May 20, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.158%
(53rd percentile)

Weaknesses

CVE ID

CVE-2018-17419

GHSA ID

GHSA-9jcx-pr2f-qvq5

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.