The gh-release npm package, designed to streamline the process of creating GitHub releases for Node.js packages, saw a minor version update from 1.0.4 to 1.0.5 on February 8th, 2015. While the core functionality remains consistent between the two versions – automating the often tedious task of release creation – subtle differences exist, primarily in release timing. Version 1.0.5 was published approximately 21 minutes after 1.0.4, suggesting the newer release might contain very minor fixes, adjustments, or simply a rebuild.
For developers, gh-release simplifies the release workflow by automating interactions with the GitHub API. It leverages dependencies like github for API communication, inquirer for interactive command-line prompts to guide the user through the release process (e.g., specifying tag names and release notes), and yargs for command-line argument parsing. This allows developers to create releases directly from their terminal, minimizing context switching and potential errors associated with manual processes. Both versions share the same core dependencies under the same version constraints, offering a stable and reliable experience for users seeking to automate their GitHub release workflow. If you're experiencing issues it is advised to use the latest version.
All the vulnerabilities related to the version 1.0.5 of the package
Command Injection in lodash
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
Prototype Pollution in lodash
Versions of lodash before 4.17.11 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.11 or later.
Prototype Pollution in lodash
Versions of lodash before 4.17.5 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of Object via __proto__ causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.5 or later.
Prototype Pollution in lodash
Versions of lodash before 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep allows a malicious user to modify the prototype of Object via {constructor: {prototype: {...}}} causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.12 or later.
Prototype Pollution in lodash
Versions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The functions pick, set, setWith, update, updateWith, and zipObjectDeep allow a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires manipulating objects based on user-provided property values or arrays.
This vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances.
