Lint-staged is a popular npm package that helps developers automatically lint files staged in Git, ensuring code quality and consistency. Comparing versions 8.0.4 and 8.0.3, the updates appear minimal but potentially impactful. The most notable difference lies in the staged-git-files dependency, which has been updated from version 1.1.1 to 1.1.2 in version 8.0.4. This suggests a bug fix or minor feature improvement within the staged-git-files package itself, likely related to how lint-staged identifies and processes staged files. Considering the core functionality of lint-staged revolves around this process, this is very important.
The other difference is in the dist segment, which provides info about the published status into the npm registry such as fileCount and unpackedSize that are different between the 2 versions. This is usually not relevant for developers, but it could potentially involve changes on the build process or adjustments done by the package maintaner. For developers already using lint-staged, upgrading from 8.0.3 to 8.0.4 is advisable to benefit from any bug fixes or improvements in identifying staged files. New users will automatically get 8.0.4 and will get the advantages already. Given the minimal nature of the changes, the author didn't deem necessary to create a new Major release (8.x.x) implying that there aren't any breaking changes between the 2 versions.
All the vulnerabilities related to the version 8.0.4 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.
