Ts-loader is a webpack loader that allows developers to use TypeScript within their webpack builds. Versions 0.3.2 and 0.3.3 share a common foundation, both being licensed under MIT and authored by James Brantly. They provide the core functionality of compiling TypeScript code leveraging dependencies like colors for terminal output styling, typescript itself for the compilation, loader-utils and object-assign for internal functionalities of the loader. Crucially, both support TypeScript version ^1.4.1. Developers already working with TypeScript 1.4.1 wouldn't see immediate benefits from upgrading dependency perspective in this minor patch,
The key difference lies in the release date. Version 0.3.3 was released on March 13, 2015, a few weeks after version 0.3.2 released on February 23, 2015. This suggests that version 0.3.3 is a patch release, likely addressing bugs or minor improvements found in 0.3.2.
For developers choosing between these versions, opting for 0.3.3 is generally recommended due to its later release date and potentially resolved issues. However, both rely on identical dependency sets and devDependencies, so stability and essential functionality are expected to be very similar. If encountering issues with webpack and JSX compilation, compatibility is indicated through the jsx-typescript devDependency. The library's source code and issue tracker are available on GitHub. When using ts-loader with webpack, consider using the latest stable version whenever possible for the best experience.
All the vulnerabilities related to the version 0.3.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...');
}