Process crash via invalid packet assertion
Published Apr 27, 2021 · Updated Nov 19, 2024
A reported reachable assertion in dname_pkt_copy in NLnet Labs Unbound before 1.9.5 crashes code that processes an invalid packet. The audit found that malformed packet data reaches assert() inside the domain-name copy routine, terminating execution when the invariant check fails. NLnet Labs disputes the vulnerability because a running installation cannot reach this condition from either remote or local input, leaving no demonstrated service impact.
Summary
What happened
A reported reachable assertion in dname_pkt_copy in NLnet Labs Unbound before 1.9.5 crashes code that processes an invalid packet. The audit found that malformed packet data reaches assert() inside the domain-name copy routine, terminating execution when the invariant check fails. NLnet Labs disputes the vulnerability because a running installation cannot reach this condition from either remote or local input, leaving no demonstrated service impact.
The record
- CVE
- CVE-2019-25037
- Published
- Apr 27, 2021
- Updated
- Nov 19, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-617
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 27, 2021CVE publishedPublication date reported by the CVE source.
- Nov 19, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo