Local code execution via overlong filename argument
Published Jan 17, 2024 · Updated Sep 10, 2024
Buffer overflow in Explorer++ 1.3.5.531 allows local users to execute arbitrary code through an overlong filename argument. The legacy command-line handler fails to bound the filename argument, allowing control of Structured Exception Handler records and redirection of execution. Exploitation requires local low-privileged access and user interaction; successful exception-chain control runs code in the Explorer++ process.
Summary
What happened
Buffer overflow in Explorer++ 1.3.5.531 allows local users to execute arbitrary code through an overlong filename argument. The legacy command-line handler fails to bound the filename argument, allowing control of Structured Exception Handler records and redirection of execution. Exploitation requires local low-privileged access and user interaction; successful exception-chain control runs code in the Explorer++ process.
The record
- CVE
- CVE-2024-0645
- Published
- Jan 17, 2024
- Updated
- Sep 10, 2024
- Vendor
- Explorerplusplus
- Product
- Explorer++
- Classifications
- CWE-120, CWE-119, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 17, 2024CVE publishedPublication date reported by the CVE source.
- Sep 10, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.3.5.531
What conditions does exploitation require?
What is affected?
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