Summary
Command Injection in ungit
Versions of ungit prior to 0.9.0 are affected by a command injection vulnerability in the url parameter.
Impact
Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Update version 0.9.0 or later.
Frequently Asked Questions
- What is CVE-2015-4130? CVE-2015-4130 is a critical-severity command injection vulnerability in ungit (npm), affecting versions <= 0.8.4. It is fixed in 0.9.0. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
- Which versions of ungit are affected by CVE-2015-4130? ungit (npm) versions <= 0.8.4 is affected.
- Is there a fix for CVE-2015-4130? Yes. CVE-2015-4130 is fixed in 0.9.0. Upgrade to this version or later.
- Is CVE-2015-4130 exploitable, and should I be worried? Whether CVE-2015-4130 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2015-4130 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2015-4130? Upgrade
ungitto 0.9.0 or later.