Local code execution via oversized filename
Published Oct 7, 2024 · Updated Oct 7, 2024
Buffer overflow in WinHex 16.1 SR-1 and 20.4 allows local users to execute arbitrary code through a long filename argument. WinHex filename handling fails to enforce a memory-buffer boundary, allowing an oversized argument to overwrite Structured Exception Handler registers. Exploitation requires low-privileged local access and user interaction, and successful control-flow hijacking executes code in the affected user's context.
Summary
What happened
Buffer overflow in WinHex 16.1 SR-1 and 20.4 allows local users to execute arbitrary code through a long filename argument. WinHex filename handling fails to enforce a memory-buffer boundary, allowing an oversized argument to overwrite Structured Exception Handler registers. Exploitation requires low-privileged local access and user interaction, and successful control-flow hijacking executes code in the affected user's context.
The record
- CVE
- CVE-2023-6362
- Published
- Oct 7, 2024
- Updated
- Oct 7, 2024
- Vendor
- X-Ways Software Technology AG
- Product
- WinHex
- Classifications
- CWE-119, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2024CVE publishedPublication date reported by the CVE source.
- Oct 7, 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=16.1sr-1
- Affected versionversion=16.1 SR-1
- Affected versionversion=20.4
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