Authenticated code execution via writable devcpp.exe binary
Published May 23, 2022 · Updated Aug 3, 2024
Incorrect default permissions in Bloodshed Dev-C++ 4.9.9.2 allow remote authenticated users to run code by replacing devcpp.exe. The installation leaves devcpp.exe and its containing directory writable, permitting substitution of a malicious executable that Dev-C++ later launches. A low-privileged account with write access to the installation is sufficient; the substituted code runs in the launching account's context.
Summary
What happened
Incorrect default permissions in Bloodshed Dev-C++ 4.9.9.2 allow remote authenticated users to run code by replacing devcpp.exe. The installation leaves devcpp.exe and its containing directory writable, permitting substitution of a malicious executable that Dev-C++ later launches. A low-privileged account with write access to the installation is sufficient; the substituted code runs in the launching account's context.
The record
- CVE
- CVE-2022-28999
- Published
- May 23, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-276, T1574
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 23, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- Dev-Cpp BloodShed Incorrect Install Permissionproof 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