Lint-staged, a popular tool for running linters against staged git files, saw a minor version update from 8.0.5 to 8.1.0. Both versions share the same core functionality of preventing messy commits by ensuring code quality before it's committed. Users can expect consistent performance in basic linting tasks and the same easy integration into existing Git workflows with both versions.
Looking at the dependencies, the key difference between these versions lies in their cosmiconfig dependency, updated from version 5.0.2 to 5.0.6. Cosmiconfig handles configuration file loading, and the update likely addresses bug fixes and performance improvements, allowing lint-staged to more reliably read configuration files like .lintstagedrc.js. While most users likely won't notice this directly, it contributes to a more robust configuration process.
A more visible change can be seen in the devDependencies. Husky, used for Git hooks, jumps from version 0.14.3 in 8.0.5 to version ^1.1.4 in 8.1.0. Additionally version 8.1.0 features a more recent version of jest-validate: ^23.5.0 compared to the previous version, where it was not present. Developers who manually manage their husky configuration or rely on specific husky features may want to review the husky changelog to ensure compatibility and take advantage of new features. Likewise, the addition of jest-validate and updates in other devDependencies hint at improvements in the testing and development lifecycle of lint-staged itself, contributing to its overall stability and reliability. In summary, version 8.1.0 offers incremental improvements and bug fixes focused on configurability and internal development workflows.
All the vulnerabilities related to the version 8.1.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.
