Memory corruption via assemble_file stack overflow
Published Aug 11, 2025 · Updated Aug 12, 2025
Stack-based buffer overflow in NASM 2.17rc0 allows local users to corrupt process memory via crafted assembly input. The public record identifies assemble_file in nasm.c but does not disclose the input field, copy operation, or missing bounds check that overruns the stack buffer. A low-privileged local account is required, and the available evidence does not establish whether exploitation exceeds a NASM process crash.
Summary
What happened
Stack-based buffer overflow in NASM 2.17rc0 allows local users to corrupt process memory via crafted assembly input. The public record identifies assemble_file in nasm.c but does not disclose the input field, copy operation, or missing bounds check that overruns the stack buffer. A low-privileged local account is required, and the available evidence does not establish whether exploitation exceeds a NASM process crash.
The record
- CVE
- CVE-2025-8845
- Published
- Aug 11, 2025
- Updated
- Aug 12, 2025
- Vendor
- NASM
- Product
- NASM
- Classifications
- CWE-121, CWE-119
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2025CVE publishedPublication date reported by the CVE source.
- Aug 12, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.17rc0
What conditions does exploitation require?
What is affected?
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
- CVE-2025-8845 proof-of-concept artifactproof of concept · unverified
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