HtmlWebpackPlugin v3.0.8 is a minor update to v3.0.7 of the popular webpack plugin that simplifies the creation of HTML files to serve webpack bundles. Both versions share the same core functionality and dependencies, including lodash, tapable, toposort, loader-utils, pretty-error, html-minifier, and util.promisify. Developers can expect consistent behavior in terms of generating HTML from templates and injecting webpack-generated assets. The devDependencies, crucial for development and testing, also remain identical, ensuring consistency in the development environment. These include tools like jade, rimraf, jasmine, webpack, and various loaders for CSS, URLs, files, and HTML.
The key difference lies in the dist data, specifically the unpackedSize. Version 3.0.8 has an unpacked size of 70807 bytes, slightly larger than version 3.0.7's 67555 bytes. This suggests minor code adjustments, potentially bug fixes or small feature enhancements, that don't significantly alter the plugin's overall API or usage.
For developers, this implies a seamless upgrade experience. While a detailed changelog would pinpoint the exact modifications, the similar versions suggest a low-risk update. If you're using HtmlWebpackPlugin for HTML generation and asset injection in your webpack projects, upgrading from 3.0.7 to 3.0.8 should be straightforward. Keep an eye on the official repository or npm page for specific release notes detailing the changes. Both versions maintain the same peer dependencies for webpack, supporting versions 1.x, 2.x, 3.x, and 4.x.
All the vulnerabilities related to the version 3.0.8 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.