Code execution via long filename heap overflow
Published Jan 31, 2024 · Updated May 29, 2025
Heap-based buffer overflow in Angus Johnson Resource Hacker 3.6.0.92 allows local users to execute code via a long filename argument. INCIBE has not identified the filename-processing function or disclosed how the argument overruns its heap allocation. Exploitation requires low privileges and user interaction, and successful exploitation executes code with the affected process's privileges.
Summary
What happened
Heap-based buffer overflow in Angus Johnson Resource Hacker 3.6.0.92 allows local users to execute code via a long filename argument. INCIBE has not identified the filename-processing function or disclosed how the argument overruns its heap allocation. Exploitation requires low privileges and user interaction, and successful exploitation executes code with the affected process's privileges.
The record
- CVE
- CVE-2024-1112
- Published
- Jan 31, 2024
- Updated
- May 29, 2025
- Vendor
- Angus Johnson
- Product
- Resource Hacker
- Classifications
- CWE-119, CWE-787, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 31, 2024CVE publishedPublication date reported by the CVE source.
- May 29, 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=3.6.0.92
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
- Resource Hacker heap-overflow proof of conceptproof 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