Lint-staged is a popular npm package that helps developers automatically lint files staged in Git, ensuring code quality before commits. Comparing versions 8.0.3 and 8.0.2, the most notable difference lies in the release date and potentially very minor internal adjustments. Version 8.0.3 was released on October 30, 2018, while version 8.0.2 was released on October 29, 2018. The small difference in unpackedSize of 47092 vs 47097 could indicate some very small adjustments. Typically, patch versions like this involve bug fixes, performance tweaks, or minor dependency updates that don't introduce breaking changes.
For developers considering using lint-staged, it's important to know that both versions share the same core dependencies and development dependencies, including tools like del, execa, listr, jest, husky, eslint, and prettier. This means the functionality and integration with these tools remain consistent across both versions. If you are already using 8.0.2, upgrading to 8.0.3 is likely a safe and straightforward process that could bring subtle stability improvements. It's always a good practice to review the commit history or changelog (if available) on the project's GitHub repository for precise details on any specific changes implemented in 8.0.3. Prioritize upgrading if you've encountered any issues addressed by bug fixes after the 8.0.2 release.
All the vulnerabilities related to the version 8.0.3 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.
