dbcve.org
ShcApplication · Neurobin

CVE-2025-9174

HIGH · 7.8 CVSS v3.1 Published 2025-08-19
Fix available
A fix is available. Upgrade to after 4.0.3 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was determined in neurobin shc up to 4.0.3. This vulnerability affects the function make of the file src/shc.c of the component Filename Handler. Executing manipulation can lead to os command injection. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A command injection vulnerability exists in the filename handler of neurobin shc up to version 4.0.3. The 'make' function in src/shc.c fails to properly sanitize filenames before using them in OS command execution, allowing local attackers to inject arbitrary shell commands through specially crafted filenames.

MitigationUpgrade to shc version 4.0.4 or later to obtain the patched version. If immediate upgrading is not feasible, avoid processing untrusted filenames with shc and implement strict input validation on any filenames passed to the tool.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ShcApplication
Affected:<= 4.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if shc is installed
    Run 'which shc' or 'whereis shc' to locate the shc binary on the system
    Affected if shc is found on the system - proceed to version check
  2. Determine the installed shc version
    Run 'shc -V' or 'shc --version' to obtain the version number of the installed shc binary
    Affected if Version is 4.0.3 or lower - the system has a vulnerable version
  3. Confirm the shc implementation
    Check if the binary is the neurobin shc variant by examining the version output or running 'shc -h' to see the help/author information
    Affected if The output indicates neurobin shc (or shows no variant information with version <= 4.0.3)
  4. Verify the vulnerable code path is reachable
    The vulnerability exists in the 'make' function in src/shc.c which is invoked when shc compiles a shell script. If shc is installed and can be used to compile any shell script, the vulnerable code path is reachable
    Affected if shc is functional and can process shell script filenames - this is the default behavior when using shc to compile scripts

If neurobin shc version 4.0.3 or lower is installed and functional on the system, the command injection vulnerability in the filename handler is present and exploitable when processing any filename.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 4.0.3
Interim mitigation

Upgrade to shc version 4.0.4 or later to obtain the patched version. If immediate upgrading is not feasible, avoid processing untrusted filenames with shc and implement strict input validation on any filenames passed to the tool.

Recommended fix Moderate confidence

shc version 4.0.4 (latest release on neurobin/shc GitHub repository)

  1. 1. Identify the current shc version installed (e.g., shc -V or check package manager)
  2. 2. Download the latest stable release from the official neurobin/shc GitHub repository
  3. 3. Remove the existing installation (e.g., make uninstall or package manager removal)
  4. 4. Extract the new source tarball and navigate to the source directory
  5. 5. Compile the new version: ./configure && make
  6. 6. Install the compiled binary: make install
  7. 7. Verify the new version shows 4.0.4 or later: shc -V
Caveat Minimal risk - this is a bugfix release addressing a security vulnerability; no API changes expected for a tool of this nature

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Shc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-9174 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-9174 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data