Babel-loader is a crucial webpack module loader that allows developers to seamlessly integrate Babel, a JavaScript compiler, into their webpack build process. This integration enables the use of next-generation JavaScript features and syntax, transpiling them into code compatible with older browsers and environments.
Comparing babel-loader version 6.1.0 with its predecessor, 6.0.1, reveals subtle but important updates. Both versions share identical core dependencies like loader-utils and object-assign, along with development dependencies for testing and linting, including jscs, mocha, jshint, webpack, istanbul, and expect.js. They also maintain webpack and babel-core as peerDependencies, signaling their reliance on these packages being installed separately in the project.
The key difference lies within the release date. Version 6.1.0 arrived on November 9, 2015, a week after version 6.0.1 released on November 2, 2015. This suggests that version 6.1.0 likely contains bug fixes, performance improvements, or minor feature enhancements over 6.0.1. Given the short timeframe, the changes are unlikely to be groundbreaking, but beneficial to users nonetheless.
For developers using babel-loader, these versions confirm its ongoing maintenance and commitment to compatibility with Babel 6 and Webpack. By leveraging babel-loader, projects can confidently adopt latest JavaScript syntax and features, empowering developers to write cleaner, more modern code that functions across diverse environments. Developers seeking the most up-to-date fixes and enhancements should prefer the newer 6.1.0 version.
All the vulnerabilities related to the version 6.1.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...');
}