Memory corruption via pre-check compressed-name copy
Published Apr 27, 2021 · Updated Aug 5, 2024
Out-of-bounds write in rdata_copy in NLnet Labs Unbound before 1.9.5 allows attackers to corrupt memory via a compressed DNS name. The function calls memmove before its log_assert check when len exceeds pkt_len, so copying occurs before the oversized length is rejected. Upstream disputes the vulnerability because earlier packet-parsing checks prevent remote or local inputs from reaching this state in a running installation.
Summary
What happened
Out-of-bounds write in rdata_copy in NLnet Labs Unbound before 1.9.5 allows attackers to corrupt memory via a compressed DNS name. The function calls memmove before its log_assert check when len exceeds pkt_len, so copying occurs before the oversized length is rejected. Upstream disputes the vulnerability because earlier packet-parsing checks prevent remote or local inputs from reaching this state in a running installation.
The record
- CVE
- CVE-2019-25042
- Published
- Apr 27, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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
- X41 Unbound audit rdata_copy proof of conceptproof of concept · demonstrated
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