Local code execution via SEH pointer overwrite
Published Jun 1, 2026 · Updated Jun 1, 2026
Stack-based buffer overflow in ArmCode Arm Whois 3.11 allows local users to execute arbitrary code through a crafted input file. The application copies file content without a sufficient bounds check, allowing data at a 672-byte offset to overwrite the nSEH and SEH pointers. Exploitation requires local ability to supply the file, and successful exception-handler hijacking executes code within the Arm Whois process.
Summary
What happened
Stack-based buffer overflow in ArmCode Arm Whois 3.11 allows local users to execute arbitrary code through a crafted input file. The application copies file content without a sufficient bounds check, allowing data at a 672-byte offset to overwrite the nSEH and SEH pointers. Exploitation requires local ability to supply the file, and successful exception-handler hijacking executes code within the Arm Whois process.
The record
- CVE
- CVE-2018-25432
- Published
- Jun 1, 2026
- Updated
- Jun 1, 2026
- Vendor
- ArmCode
- Product
- Arm Whois
- Classifications
- CWE-120, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 1, 2026CVE publishedPublication date reported by the CVE source.
- Jun 1, 2026Record 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=3.11
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
- Arm Whois 3.11 - Buffer Overflow (ASLR)functional · 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