How severe is CVE-2015-4130?

No CVSS score has been assigned to CVE-2015-4130 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2015-4130?

CVE-2015-4130 affects the following packages: ungit (npm). Ecosystems affected: npm.

How do I fix CVE-2015-4130?

Update ungit to 0.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-4130 is resolved across your whole dependency graph.

How do I detect CVE-2015-4130 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ungit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2015-4130 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2015-4130 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-4130 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2015-4130 published, and has it been updated?

CVE-2015-4130 was published on August 31, 2020 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2015-4130 — ungit

CVE-2015-4130 is a remote code execution vulnerability in ungit. A fix is available for ungit — see the affected versions and patch details below.

Command Injection in ungit

Published

Aug 31, 2020

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

3other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

ungitnpm

489downloads / week

Description

Versions of ungit prior to 0.9.0 are affected by a command injection vulnerability in the url parameter.

Recommendation

Update version 0.9.0 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`ungit`	all versions	0.9.0`npm install ungit@0.9.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ungit, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ungit to 0.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-4130 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

Versions of `ungit` prior to 0.9.0 are affected by a command injection vulnerability in the `url` parameter. ## Recommendation Update version 0.9.0 or later.

O3 Security · Impact-Aware SCA

Is CVE-2015-4130 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works