Lint-staged is a popular npm package that streamlines the process of running linters and formatters on files staged in Git, ensuring code quality and consistency before commits. Comparing versions 8.2.1 and 8.2.0 reveals subtle but potentially impactful changes for developers. Both versions share identical core dependencies and development dependencies, indicating a focus on stability and maintaining existing functionalities. The shared dependencies include essential tools like del for file deletion, yup for schema validation, execa for executing commands, listr for creating elegant task lists, and cosmiconfig for configuration file management.
However, a key difference lies in the dist object. Version 8.2.1 has an unpackedSize of 50185 bytes, slightly larger than version 8.2.0's 49977 bytes. This suggests minor code additions or adjustments, potentially bug fixes or performance improvements. Most importantly, version 8.2.1 was released on 2019-06-13, a week after version 8.2.0 (2019-06-06). This one-week difference underscores the incremental nature of the update, hinting at a quick resolution of any issues found in the preceding stable release.
Developers already using lint-staged should consider upgrading to 8.2.1 for potential stability improvements and bug fixes. New users can confidently rely on version 8.2.1 as a refined and up-to-date tool for integrating linting and formatting into their Git workflow, promoting cleaner code and collaboration.
All the vulnerabilities related to the version 8.2.1 of the package
Prototype Pollution in property-expr
The package property-expr before 2.0.3 are vulnerable to Prototype Pollution via the setter function.
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.
