Application crash via slaxLexer null pointer dereference
Published Sep 20, 2021 · Updated Aug 4, 2024
NULL pointer dereference in libslax 0.22.1 and earlier allows remote attackers to crash slaxproc through a crafted SLAX file. The CVE record identifies slaxLexer in slaxlexer.c but does not disclose the parser state or value that becomes null; its linked upstream issue instead demonstrates an out-of-bounds read in the same function. Exploitation requires an application or user to pass attacker-controlled SLAX input to the parser, and the documented consequence is process termination rather than code execution or data access.
Summary
What happened
NULL pointer dereference in libslax 0.22.1 and earlier allows remote attackers to crash slaxproc through a crafted SLAX file. The CVE record identifies slaxLexer in slaxlexer.c but does not disclose the parser state or value that becomes null; its linked upstream issue instead demonstrates an out-of-bounds read in the same function. Exploitation requires an application or user to pass attacker-controlled SLAX input to the parser, and the documented consequence is process termination rather than code execution or data access.
The record
- CVE
- CVE-2021-39532
- Published
- Sep 20, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
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.
Weakness, pattern, technique
Public exploit references
- heap-overflow-slaxLexer-slaxlexer-1107.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