Local code execution via SEH chain overwrite
Published Mar 24, 2026 · Updated Mar 24, 2026
Stack-based buffer overflow in 4Mhz Base64 Decoder 1.1.2 allows local users to execute arbitrary code via a crafted input file. Processing the oversized file writes beyond a stack buffer and replaces the SEH chain with a POP-POP-RET address that redirects execution to an egghunter payload. The file must be processed locally; successful exploitation runs shellcode with the application's privileges on Windows.
Summary
What happened
Stack-based buffer overflow in 4Mhz Base64 Decoder 1.1.2 allows local users to execute arbitrary code via a crafted input file. Processing the oversized file writes beyond a stack buffer and replaces the SEH chain with a POP-POP-RET address that redirects execution to an egghunter payload. The file must be processed locally; successful exploitation runs shellcode with the application's privileges on Windows.
The record
- CVE
- CVE-2019-25634
- Published
- Mar 24, 2026
- Updated
- Mar 24, 2026
- Vendor
- 4Mhz
- Product
- Base64 Decoder
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2026CVE publishedPublication date reported by the CVE source.
- Mar 24, 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=1.1.2
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.
Public exploit references
- Base64 Decoder 1.1.2 Local Buffer Overflow (SEH Egghunter)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