HtmlWebpackPlugin simplifies the creation of HTML files specifically designed to serve webpack bundles. Comparing versions 2.14.0 and 2.13.0, the core functionality remains consistent, focusing on streamlining the inclusion of generated webpack assets in HTML. Both versions share identical dependencies, including lodash, bluebird, toposort, loader-utils, pretty-error, and html-minifier, ensuring a stable set of utilities for template manipulation, promise handling, dependency sorting, and HTML minification. Development dependencies are also identical: jade, rimraf, jasmine, webpack, css-loader, url-loader, dir-compare, es6-promise, file-loader, html-loader, jade-loader, semistandard, style-loader, appcache-webpack-plugin, underscore-template-loader, extract-text-webpack-plugin, and webpack-recompilation-simulator. This means that developers upgrading from 2.13.0 to 2.14.0 can expect a seamless transition with no breaking changes introduced by dependency updates. The primary difference lies in the release date; version 2.14.0 was released a few minutes after version 2.13.0. While subtle changes or bug fixes may exist, they are not explicitly outlined through dependency modifications. Developers leveraging HtmlWebpackPlugin can continue relying on it for automated HTML generation, dynamic asset insertion, and simplified webpack integration. Those looking for specific fixes might investigate the commit history between these releases, but the absence of dependency alterations suggests the update primarily involves behind-the-scenes improvements or very minor adjustments. Upgrade with confidence, knowing the core functionality will stay the same.
All the vulnerabilities related to the version 2.14.0 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.
Regular Expression Denial of Service in clean-css
Version of clean-css prior to 4.1.11 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.
Upgrade to version 4.1.11 or higher.