HtmlWebpackPlugin simplifies the creation of HTML files to serve webpack bundles, easing the process for developers. Examining versions 3.0.7 and 3.0.6 reveals subtle differences that might impact project builds. Both versions share identical dependencies including lodash, tapable, toposort, loader-utils, pretty-error, html-minifier, and util.promisify. Similarly, their development dependencies are the same, encompassing tools like jade, rimraf, jasmine, webpack, css-loader, url-loader, dir-compare, es6-promise, file-loader, html-loader, jade-loader, semistandard, style-loader, standard-version, jasmine-diff-matchers, appcache-webpack-plugin, underscore-template-loader, extract-text-webpack-plugin, and webpack-recompilation-simulator. Peer dependencies on webpack versions 1, 2, 3, and 4 also remain consistent. Developers should also note that the author information including email and name and the repository is the same.
The versions are licenced under MIT and the fileCount is also the same with a value of 10.
The key difference lies in the unpackedSize attribute of the distributed package, where version 3.0.7 has 67555 bytes compared to 3.0.6 with 67245 bytes reflecting likely code changes and bugfixes. Furthermore, the release date reveals a two-week gap, with 3.0.7 released on March 19, 2018, and 3.0.6 on March 6, 2018. Usually it means that the newest version fixes some bug fixes. Developers should always consult the changelog of html-webpack-plugin for detailed information to determine whether upgrading from 3.0.6 to 3.0.7 is beneficial for their webpack-based projects and if it fixes some bugs they have experienced.
All the vulnerabilities related to the version 3.0.7 of the package
Prototype pollution in webpack loader-utils
Prototype pollution vulnerability in function parseQuery in parseQuery.js in webpack loader-utils prior to version 2.0.3 via the name variable in parseQuery.js.
Prototype Pollution in JSON5 via Parse Method
The parse method of the JSON5 library before and including version 2.2.1 does not restrict parsing of keys named __proto__, allowing specially crafted strings to pollute the prototype of the resulting object.
This vulnerability pollutes the prototype of the object returned by JSON5.parse and not the global Object prototype, which is the commonly understood definition of Prototype Pollution. However, polluting the prototype of a single object can have significant security impact for an application if the object is later used in trusted operations.
This vulnerability could allow an attacker to set arbitrary and unexpected keys on the object returned from JSON5.parse. The actual impact will depend on how applications utilize the returned object and how they filter unwanted keys, but could include denial of service, cross-site scripting, elevation of privilege, and in extreme cases, remote code execution.
This vulnerability is patched in json5 v2.2.2 and later. A patch has also been backported for json5 v1 in versions v1.0.2 and later.
Suppose a developer wants to allow users and admins to perform some risky operation, but they want to restrict what non-admins can do. To accomplish this, they accept a JSON blob from the user, parse it using JSON5.parse, confirm that the provided data does not set some sensitive keys, and then performs the risky operation using the validated data:
const JSON5 = require('json5');
const doSomethingDangerous = (props) => {
if (props.isAdmin) {
console.log('Doing dangerous thing as admin.');
} else {
console.log('Doing dangerous thing as user.');
}
};
const secCheckKeysSet = (obj, searchKeys) => {
let searchKeyFound = false;
Object.keys(obj).forEach((key) => {
if (searchKeys.indexOf(key) > -1) {
searchKeyFound = true;
}
});
return searchKeyFound;
};
const props = JSON5.parse('{"foo": "bar"}');
if (!secCheckKeysSet(props, ['isAdmin', 'isMod'])) {
doSomethingDangerous(props); // "Doing dangerous thing as user."
} else {
throw new Error('Forbidden...');
}
If the user attempts to set the isAdmin key, their request will be rejected:
const props = JSON5.parse('{"foo": "bar", "isAdmin": true}');
if (!secCheckKeysSet(props, ['isAdmin', 'isMod'])) {
doSomethingDangerous(props);
} else {
throw new Error('Forbidden...'); // Error: Forbidden...
}
However, users can instead set the __proto__ key to {"isAdmin": true}. JSON5 will parse this key and will set the isAdmin key on the prototype of the returned object, allowing the user to bypass the security check and run their request as an admin:
const props = JSON5.parse('{"foo": "bar", "__proto__": {"isAdmin": true}}');
if (!secCheckKeysSet(props, ['isAdmin', 'isMod'])) {
doSomethingDangerous(props); // "Doing dangerous thing as admin."
} else {
throw new Error('Forbidden...');
}
kangax html-minifier REDoS vulnerability
A Regular Expression Denial of Service (ReDoS) flaw was found in kangax html-minifier 4.0.0 because of the reCustomIgnore regular expression.