HtmlWebpackPlugin versions 3.0.0 and 3.0.1 are closely related, offering developers a streamlined approach to generating HTML files that seamlessly integrate with webpack bundles. Both versions share the primary goal of simplifying the creation of HTML files needed to serve webpack bundles. Key dependencies like lodash, tapable, and html-minifier are consistent across both releases, ensuring core functionality remains stable. The developer tooling is also very similar, leveraging tools like Jasmine for testing, and webpack, css-loader, url-loader for building and developing the plugin itself.
A notable difference appears in the peerDependencies, where version 3.0.0 explicitly declares extract-text-webpack-plugin as a peer dependency with a specified version range, while 3.0.1 removes this dependency entirely. This subtle change could impact compatibility with particular project setups using older versions of extract-text-webpack-plugin, so developers utilising this plugin should carefully evaluate the implications of upgrading. The slight variance in fileCount and unpackedSize in the dist object suggests minor internal adjustments or packaging refinements. The 'releaseDate' also shows that there is only a 1 day difference between the releases, therefore there must have been a very minor fix done in the newer version
For developers, HtmlWebpackPlugin simplifies the process of injecting webpack-generated assets (like JavaScript and CSS files) into HTML templates. These versions continue to support a wide variety of webpack versions, indicated by "webpack": "^1.0.0 || ^2.0.0 || ^3.0.0 || ^4.0.0" as a peer dependency. The upgrade from 3.0.0 to 3.0.1 seems incremental so evaluating the peer dependency change related to extract-text-webpack-plugin, before upgrading your project is a good idea.
All the vulnerabilities related to the version 3.0.1 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.