Assembler crash via null IEEE segment name
Published Aug 22, 2023 · Updated Aug 4, 2024
Null-pointer dereference in NASM 2.14.03 and 2.15 allows attackers to crash the assembler by processing a crafted assembly file. The ieee_segment function in output/outieee.c can leave seg->name null after label handling and dereference the unset pointer while defining later IEEE 695 segments. Execution requires a user or build process to invoke NASM on attacker-supplied IEEE-output input, and the resulting segmentation fault terminates that NASM process.
Summary
What happened
Null-pointer dereference in NASM 2.14.03 and 2.15 allows attackers to crash the assembler by processing a crafted assembly file. The ieee_segment function in output/outieee.c can leave seg->name null after label handling and dereference the unset pointer while defining later IEEE 695 segments. Execution requires a user or build process to invoke NASM on attacker-supplied IEEE-output input, and the resulting segmentation fault terminates that NASM process.
The record
- CVE
- CVE-2020-21528
- Published
- Aug 22, 2023
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 22, 2023CVE 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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