Sass-loader versions 3.2.3 and 3.2.2 are webpack loaders streamlining Sass and SCSS file integration into your projects. Both versions share the same core functionality and MIT license, ensuring ease of use within various project types. They are developed by J. Tangelder and hosted on GitHub. A primary use case for both versions involves simplifying the management and dependency resolution around including sass and scss files within larger Javascript projects.
Version 3.2.3, released on June 27, 2016, features updated dependencies like loader-utils (to ^0.2.5) and object-assign (to ^4.0.1). Developers should note the testing and build environment relies on specific versions of mocha, jshint, should, webpack, node-sass, and other loaders and utilities which will guarantee a smoother experience when integrating into older stacks.
The immediate predecessor, version 3.2.2, released a day earlier on June 26, 2016, incorporates slightly different dependency constraints such as loader-utils (^0.2.15) and object-assign (^4.1.0), newer dev dependencies and matching node-sass version in peerDependencies. Although the core functionality remains the same and webpack and node-sass peer dependencies are similar, developers should upgrade with caution, testing thoroughly for any minor breaking changes introduced by the updated utilities. Both versions declare webpack and node-sass as peer dependencies, indicating they rely on these packages being installed separately. If upgrading to versions beyond these, careful consideration should be given to compatibility with project tooling.
All the vulnerabilities related to the version 3.2.3 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...');
}