Local command execution via unquoted CC variable
Published Aug 19, 2025 · Updated Aug 20, 2025
Command injection in Neurobin SHC 4.0.0 through 4.0.3 allows local users to execute shell commands through the CC variable. The make() function in generated hardened executables reads CC, embeds it unquoted in a compiler command with sprintf(), and passes the string to system(). Exploitation requires local execution of a binary produced with hardening enabled and runs injected shell commands with that binary's privileges.
Summary
What happened
Command injection in Neurobin SHC 4.0.0 through 4.0.3 allows local users to execute shell commands through the CC variable. The make() function in generated hardened executables reads CC, embeds it unquoted in a compiler command with sprintf(), and passes the string to system(). Exploitation requires local execution of a binary produced with hardening enabled and runs injected shell commands with that binary's privileges.
The record
- CVE
- CVE-2025-9176
- Published
- Aug 19, 2025
- Updated
- Aug 20, 2025
- Vendor
- Neurobin
- Product
- SHC (Shell Script Compiler)
- Classifications
- CWE-78, CWE-77, T1059.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2025CVE publishedPublication date reported by the CVE source.
- Aug 20, 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=4.0.0
- Affected versionversion=4.0.1
- Affected versionversion=4.0.2
- Affected versionversion=4.0.3
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