Shelljs version 0.1.4 arrives as a minor update to version 0.1.3, maintaining its core purpose: providing portable Unix shell commands for Node.js environments. This allows developers to execute common shell operations directly from JavaScript code, streamlining tasks such as file manipulation, process execution, and directory management. Both versions share the same author and repository, indicating a continuity in development and maintenance by Artur Adib.
The most notable change from version 0.1.3 to 0.1.4 lies in the dependency management. Version 0.1.3 lists 'jshint' as a dependency, while version 0.1.4 moves 'jshint' to the 'devDependencies' section. This signals a shift where JSHint, a JavaScript code quality tool, is now primarily used for development-time linting, ensuring code style and preventing errors during development of shelljs itself, rather than being a mandatory dependency for users of the library. For developers incorporating Shelljs into their projects, this suggests a lighter install footprint, as the JSHint tooling won't be included with the package. Version 0.1.4 was released on May 10th, 2013, about three weeks after version 0.1.3. This quick update hints at either a bug fix or a minor improvement in the new version. Developers should note difference in dependencies between versions
All the vulnerabilities related to the version 0.1.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: