Sass-loader versions 3.2.2 and 3.2.1 are webpack loaders that allow developers to import Sass and SCSS files directly into their JavaScript modules. Comparing the two versions, a few key differences emerge that could impact development workflows.
The most immediate change is in the dependencies loader-utils and object-assign. Version 3.2.2 updates loader-utils from 0.2.5 to 0.2.15 and object-assign from 4.0.1 to 4.1.0, potentially bringing in bug fixes, performance enhancements, and new features from those libraries. Also the node-sass version was updated from 3.4.2 to ^3.8.0
Furthermore, there are updates to the development dependencies. Version 3.2.2 includes newer versions of mocha, jshint, should, webpack, css-loader, and style-loader. These updates likely incorporate improvements in testing frameworks, code linting, module bundling, and CSS handling, ensuring a smoother development experience. Specifically, the update of webpack from version 1.12.14 to ^1.13.1 in development dependencies suggests compatibility with newer webpack features and optimizations, which might be relevant for developers using Sass-loader in complex webpack configurations. The update to css-loader from version ^0.23.0 is as well important.
Developers should evaluate these changes based on their project's dependency requirements and the specific features they utilize from Sass-loader. The updated dependencies in version 3.2.2 could offer benefits in terms of stability, performance, and compatibility, but it's essential to ensure compatibility with existing project configurations. The release dates also reveal that version 3.2.2 was released about week after 3.2.1.
All the vulnerabilities related to the version 3.2.2 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...');
}