Service crash via out-of-bounds comment parsing
Published Sep 20, 2021 · Updated Aug 4, 2024
Heap-buffer over-read in libslax 0.22.1 and earlier allows context-dependent attackers to crash a consuming process with crafted SLAX input. While testing whether input begins a comment, slaxIsCommentStart reads one byte past the heap buffer when crafted input ends at the boundary. A consuming application must parse the attacker-controlled content; the demonstrated consequence is an AddressSanitizer-detected abort, not code execution.
Summary
What happened
Heap-buffer over-read in libslax 0.22.1 and earlier allows context-dependent attackers to crash a consuming process with crafted SLAX input. While testing whether input begins a comment, slaxIsCommentStart reads one byte past the heap buffer when crafted input ends at the boundary. A consuming application must parse the attacker-controlled content; the demonstrated consequence is an AddressSanitizer-detected abort, not code execution.
The record
- CVE
- CVE-2021-39534
- Published
- Sep 20, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 20, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
Public exploit references
- heap-overflow-slaxIsCommentStart-slaxlexer-751.zipproof 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