Memory corruption via unchecked parenthesized newline handling
Published Apr 27, 2021 · Updated Aug 5, 2024
An out-of-bounds write in sldns_bget_token_par affects NLnet Labs Unbound before 1.9.5 during buffered token parsing. The parser replaces a parenthesized newline with a space by advancing the token pointer without first checking the supplied buffer limit. NLnet Labs disputes the vulnerability because a running Unbound installation cannot reach the defective path through remote or local input.
Summary
What happened
An out-of-bounds write in sldns_bget_token_par affects NLnet Labs Unbound before 1.9.5 during buffered token parsing. The parser replaces a parenthesized newline with a space by advancing the token pointer without first checking the supplied buffer limit. NLnet Labs disputes the vulnerability because a running Unbound installation cannot reach the defective path through remote or local input.
The record
- CVE
- CVE-2019-25035
- 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
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