Lint-staged version 8.0.2 introduces minimal changes compared to its predecessor, version 8.0.1, both designed to automatically lint staged files using Git. Developers leveraging lint-staged can benefit from its ability to run linters against only the files that are about to be committed, ensuring a clean codebase without the need to manually lint the entire project. Both versions share identical core functionalities, dependencies, and development dependencies, indicating a stable and consistent toolset for development workflows.
The key difference lies in a minor update reflecting a bug fix or very targeted improvements. Version 8.0.2 was released just 13 minutes after 8.0.1, pointing towards a quick patch addressing a potential issue discovered immediately after the initial release. The dist object reveals a slight increase in unpackedSize from 47028 to 47097 bytes, suggesting some file modifications. While the core functionality remains the same, upgrading to 8.0.2 is recommended to ensure the most stable and reliable experience, incorporating any immediate fixes. Both versions rely on a robust suite of tools like execa for executing commands, listr for elegant task management, and cosmiconfig for configuration, giving developers a customizable linting workflow.
All the vulnerabilities related to the version 8.0.2 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.
