Gulp, the simple stream-y build helper, saw a minor version bump from 0.0.8 to 0.0.9 with a release just hours apart on July 6th, 2013. While seemingly small, this update introduces a significant change for developers managing files and workflows. The key difference lies in the introduction of a new dependency: gaze. This dependency, a file watching utility, likely enhances Gulp's ability to monitor file system changes and trigger build processes automatically. This improvement streamlines the development workflow by automating tasks whenever a file is modified.
For developers considering Gulp at this early stage, the inclusion of gaze in version 0.0.9 offers a more robust and efficient file watching capability compared to version 0.0.8. Existing users might find upgrading worthwhile to leverage this enhanced automation. Both versions share core dependencies like mkdirp, optimist, gulp-util, glob-stream, and event-stream, suggesting a consistent foundation for build processes. The development dependencies related to testing (mocha, rimraf, and should) remain identical between the two versions, indicating a focus on maintaining test coverage. This slight but crucial upgrade is worth looking at to ensure that your developments are up to date.
All the vulnerabilities related to the version 0.0.9 of the package
Prototype Pollution in minimist
Affected versions of minimist are vulnerable to prototype pollution. Arguments are not properly sanitized, allowing an attacker to modify the prototype of Object, causing the addition or modification of an existing property that will exist on all objects.
Parsing the argument --__proto__.y=Polluted adds a y property with value Polluted to all objects. The argument --__proto__=Polluted raises and uncaught error and crashes the application.
This is exploitable if attackers have control over the arguments being passed to minimist.
Upgrade to versions 0.2.1, 1.2.3 or later.
Prototype Pollution in minimist
Minimist prior to 1.2.6 and 0.2.4 is vulnerable to Prototype Pollution via file index.js, function setKey() (lines 69-95).
Command Injection in lodash
lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
