Lint-staged version 8.0.5 is a minor update to the popular npm package streamlining Git workflows by linting files before commit. Comparing it to the previous stable version, 8.0.4, reveals updated dependencies, with @iamstarkov/listr-update-renderer at version 0.4.1 replacing the direct GitHub tarball dependency listr-update-renderer used previously. This change suggests a move towards a more standard dependency management approach. Both releases maintain the core functionality, enabling developers to automatically format and lint code, improving code quality and consistency across projects. Dependencies such as del, execa, lodash, and cosmiconfig provide functionalities for file deletion, process execution, utility functions, and configuration file handling, respectively. The inclusion of husky as a dev dependency remains consistent, indicating continued support for Git hooks simplifying the integration directly into the development workflow. Developers using lint-staged can expect a reliable tool for pre-commit code checks, ensuring only clean code makes it into the repository. The update focuses on dependency management rather than significant functional changes, ensuring a smooth transition with improved library maintenance. The updated dependency @iamstarkov/listr-update-renderer enhances the visual feedback during the linting process, improving the overall user experience by providing clearer and more informative updates in the console. The releaseDate indicates that version 8.0.5 was released a few weeks after version 8.0.4, further pinpointing the freshness of this release.
All the vulnerabilities related to the version 8.0.5 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.
