Lint-staged version 8.1.7 and 8.1.6 are both tools designed to help developers maintain code quality by linting files staged in Git. These versions share a core purpose: running linters against staged files to ensure code conforms to specified standards before committing. Both versions include essential dependencies like del for file deletion, yup for schema validation, execa for executing commands, listr for creating task lists, and cosmiconfig for configuration file management. They also share the same development dependencies, including testing frameworks like jest, linting tools like eslint, and utilities like husky for Git hook integration.
A key difference between the versions lies in the cosmiconfig dependency. Version 8.1.7 uses cosmiconfig version 5.2.0 whereas version 8.1.6 uses version 5.0.2. This update in cosmiconfig likely includes bug fixes, performance improvements, or new features related to configuration file handling. This is particularly relevant for developers who rely on complex configurations for their linting process, as it should streamline the customization of lint-staged. Additionally, version 8.1.7 was released on May 15th, 2019, while version 8.1.6 was released on May 3rd, 2019 - it includes any improvements done during this period of time. The difference in the unpackedSize attribute in the dist section indicates slight differences between the versions.
All the vulnerabilities related to the version 8.1.7 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.
