Shelljs, a Node.js library providing portable Unix shell commands, saw a minor update between versions 0.0.3 and 0.0.4. While the core description remains consistent, offering developers a way to execute common shell tasks within their JavaScript environment, the key difference lies in the release date. Version 0.0.4 was published on March 22, 2012, following version 0.0.3 which was released on March 21, 2012. This very short delta between releases suggests that version 0.0.4 likely addresses a bug fix or minor improvement discovered shortly after the release of 0.0.3.
For developers considering using Shelljs, both versions provide a foundation for executing commands like ls, cp, rm, and grep directly from Node.js scripts. The absence of listed dependencies in both versions indicates a lightweight library with minimal external requirements, simplifying integration into existing projects. The repository URL points to a GitHub repository, allowing developers to inspect the source code, contribute, and report issues. Given the close release dates, it's generally recommended to use the newer version (0.0.4) to benefit from any potential bug fixes or enhancements, ensuring a more stable and reliable experience when automating shell tasks within Node.js. The library is authored by Artur Adib, which hints at a commitment to maintaining and improving this valuable tool.
All the vulnerabilities related to the version 0.0.4 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: