Unauthenticated code execution via unsanitized build filename
Published May 7, 2024 · Updated Apr 3, 2026
OS command injection in CHAOS 5.0.1 allows remote attackers to execute arbitrary code through a crafted filename in a binary-generation request. BuildClient inserts the filename into the buildStr shell command without sanitization, then passes the resulting string to sh -c. The request requires no privileges or user interaction, and successful exploitation runs commands with the CHAOS server process's privileges.
Summary
What happened
OS command injection in CHAOS 5.0.1 allows remote attackers to execute arbitrary code through a crafted filename in a binary-generation request. BuildClient inserts the filename into the buildStr shell command without sanitization, then passes the resulting string to sh -c. The request requires no privileges or user interaction, and successful exploitation runs commands with the CHAOS server process's privileges.
The record
- CVE
- CVE-2024-33434
- Published
- May 7, 2024
- Updated
- Apr 3, 2026
- Vendor
- Tiago Rodrigo Lampert
- Product
- CHAOS
- Classifications
- CWE-78, T1059.004, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 7, 2024CVE publishedPublication date reported by the CVE source.
- Apr 3, 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=- <1b451cf62582295b7225caf5a7b506f0bad56f6b
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
- Crafted filename command-injection exampleproof 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