Shelljs streamlines the execution of common Unix shell commands within Node.js environments, offering a portable and convenient way to manage system-level tasks from JavaScript code. Versions 0.0.8 and 0.0.9 both promise to simplify interactions with the operating system, abstracting away the complexities of direct system calls. Examining the metadata, there are minimal differences between the two versions beyond the release date and version number. Both appear to be dependency-free and offer the same basic description and author information pointing to Artur Adib. The repository field is identical, indicating a consistent source code origin on GitHub. For developers, this suggests the upgrade from 0.0.8 to 0.0.9 is likely a minor update, potentially including bug fixes or small feature enhancements. While the specifics of these changes aren't detailed here, developers should consider upgrading to the newer version for potential stability improvements. Shelljs remains a valuable tool for tasks like file manipulation, running external programs, and automating build processes within Node.js projects, providing a simpler alternative to writing platform-specific code. The similarity between the versions emphasizes the stability of the core library, and the clear authorship and repository details inspire confidence in its maintainability.
All the vulnerabilities related to the version 0.0.9 of the package
Improper Privilege Management in shelljs
shelljs is vulnerable to Improper Privilege Management
Improper Privilege Management in shelljs
Output from the synchronous version of shell.exec()
may be visible to other users on the same system. You may be affected if you execute shell.exec()
in multi-user Mac, Linux, or WSL environments, or if you execute shell.exec()
as the root user.
Other shelljs functions (including the asynchronous version of shell.exec()
) are not impacted.
Patched in shelljs 0.8.5
Recommended action is to upgrade to 0.8.5.
https://huntr.dev/bounties/50996581-c08e-4eed-a90e-c0bac082679c/
If you have any questions or comments about this advisory: