@npmcli/git
Affected
- introduced
0, fixed2.0.8(semver)
Fixed versions
2.0.8
Fix
- Fixed version
2.0.8npm install @npmcli/[email protected]
Advisory
Also known as: None
Arbitrary Command Injection due to Improper Command Sanitization
Summary
There exists a command injection vulnerability in npmcli/git versions <2.0.8 which may result in arbitrary shell command execution due to improper argument sanitization when npmcli/git is used to execute Git commands based on user controlled input.
The impact of this issue is possible Arbitrary Command Injection when npmcli/git is run with untrusted (user controlled) Git command arguments.
Impact
Arbitrary Command Injection
Details
npmcli/git prior to release 2.0.8 passed user controlled input as arguments to a shell command without properly sanitizing this input. Passing unsanitized input to a shell can lead to arbitrary command injection. For example passing git+https://github.com/npm/git; echo hello world would trigger the shell execution of echo hello world.
This issue was remediated by no longer running npmcli/git git commands through an intermediate shell.
Patches
This issue has been patched in release 2.0.8
Acknowledgements
This report was reported to us by @tyage (Ierae Security) through the GitHub Bug Bounty Program.
Medium Basis: The source's own band: MODERATE
0, fixed 2.0.8 (semver)2.0.8
2.0.8npm install @npmcli/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0