Ts-loader is a TypeScript loader for webpack, facilitating the integration of TypeScript code into webpack-based projects. Version 0.4.2, released on May 9, 2015, follows closely after version 0.4.1, which arrived on May 6, 2015. The core functionality remains consistent: enabling developers to use TypeScript within their webpack workflows. Both versions share the same core dependencies like colors, loader-utils, and object-assign, alongside development dependencies like mocha, webpack, and jsx-typescript. The MIT license and author information also remain unchanged.
The key difference lies in the specified version constraint for the typescript dependency and the release date. Version 0.4.1 declares a dependency on typescript version "~1.5.0", while version 0.4.2 depends on typescript version "~1.5.0-beta". This indicates that ts-loader 0.4.2 was specifically built and tested against a beta release of TypeScript 1.5.0.
For developers, this is crucial information. If you're using ts-loader, compatibility with your TypeScript version is paramount. The slight change in the typescript dependency suggests that version 0.4.2 might include fixes or adaptations specifically addressing the beta release of TypeScript 1.5.0. If you are using 1.5.0 beta is highly recommended to use 0.4.2. For projects targeting the stable TypeScript 1.5.0, version 0.4.1 might be preferable until 0.4.2 is thoroughly tested with the final release. It's always best to consult the ts-loader changelog or release notes for detailed information about specific bug fixes or new features introduced in version 0.4.2.
All the vulnerabilities related to the version 0.4.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...');
}