Quick answers
- Is CVE-2022-25912 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-25912 being exploited in the wild.
- How severe is CVE-2022-25912?
- Low severity, with a CVSS score of 3.1, published 6 December 2022.
- Which products and versions are affected?
- simple-git (npm) SEMVER:introduced=0,fixed=3.15.0.
- Is there a fix for CVE-2022-25912?
- Yes. simple-git (npm): upgrade to 3.15.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-25912 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2022-25912?
- Check whether you run simple-git (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- simple-git (npm): upgrade to 3.15.0 or later
npm install simple-git@3.15.0
Technical details
The vulnerability is an incomplete fix of CVE-2022-24066 involving OS command injection (CWE-78) in the Git transport handling mechanism. When the ext transport protocol is enabled (via the allowUnsafeProtocolOverride configuration option), the clone() method does not properly sanitize user-controlled repository URLs before passing them to shell execution. An attacker can craft a malicious repository URL containing shell metacharacters to execute arbitrary commands with the privileges of the application. The vulnerability requires the developer to explicitly enable unsafe protocol overrides, but this configuration may be enabled unknowingly or intentionally for compatibility. The fix was released in version 3.15.0.
Affected products
- simple-git simple-git < 3.15.0
Identifiers
- CVE-2022-25912
- GHSA-9p95-fxvg-qgq2
Timeline
- 2022-12-06: disclosed
- 2022-11-12: patched: Fix released in version 3.15.0