Lint-staged has a new version 8.0.0 released on October 29, 2018, following the previous stable version 7.3.0, released on September 20, 2018. Both versions serve the core purpose of linting files staged in Git, ensuring code quality before commits.
A notable change is the addition of the del dependency in version 8.0.0, used for deleting files/folders, which perhaps suggests enhancements in cleaning up temporary files or managing workspace changes. The execa dependency saw an upgrade from version 0.9.0 to 1.0.0, indicating potential improvements in executing external processes, crucial for running linters and formatters. The listr dependency was also upgraded from 0.14.1 to 0.14.2 (and depends on a custom Github repo for listr-update-renderer), likely introducing enhanced task management and display during the linting process.
In the devDependencies, version 8.0.0 upgrades jest from version 22.4.0 to 23.6.0, babel-core to version 6.26.3, and also incorporates babel-jest and jest-snapshot-serializer-ansi, and adds tmp as a dev dependency. These updates suggest improvements in testing capabilities and code transformation tooling, benefiting developers during the development and testing phases. The increased file count and unpacked size in version 8.0.0 further corroborate these additions and enhancements, making it a worthwhile upgrade for developers seeking improved linting workflows and testing tools.
All the vulnerabilities related to the version 8.0.0 of the package
Command injection in simple-git
The package simple-git before 3.3.0 is vulnerable to Command Injection via argument injection. When calling the .fetch(remote, branch, handlerFn) function, both the remote and branch parameters are passed to the git fetch subcommand. By injecting some git options, it was possible to get arbitrary command execution.
Command injection in simple-git
simple-git (maintained as git-js named repository on GitHub) is a light weight interface for running git commands in any node.js application.The package simple-git before 3.5.0 are vulnerable to Command Injection due to an incomplete fix of CVE-2022-24433 which only patches against the git fetch attack vector. A similar use of the --upload-pack feature of git is also supported for git clone, which the prior fix didn't cover. A fix was released in simple-git@3.5.0.
simple-git vulnerable to Remote Code Execution when enabling the ext transport protocol
The package simple-git before 3.15.0 is vulnerable to Remote Code Execution (RCE) when enabling the ext transport protocol, which makes it exploitable via clone() method. This vulnerability exists due to an incomplete fix of CVE-2022-24066.
Remote code execution in simple-git
Versions of the package simple-git before 3.16.0 are vulnerable to Remote Code Execution (RCE) via the clone(), pull(), push() and listRemote() methods, due to improper input sanitization. This vulnerability exists due to an incomplete fix of CVE-2022-25912.
Regular Expression Denial of Service (ReDoS) in micromatch
The NPM package micromatch prior to version 4.0.8 is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in micromatch.braces() in index.js because the pattern .* will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persisted prior to https://github.com/micromatch/micromatch/pull/266. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching.
Uncontrolled resource consumption in braces
The NPM package braces fails to limit the number of characters it can handle, which could lead to Memory Exhaustion. In lib/parse.js, if a malicious user sends "imbalanced braces" as input, the parsing will enter a loop, which will cause the program to start allocating heap memory without freeing it at any moment of the loop. Eventually, the JavaScript heap limit is reached, and the program will crash.
