Babel-core version 4.6.4 represents a minor update to the popular JavaScript transpiler library, building upon the foundation laid by version 4.6.3. Both versions serve the crucial function of converting modern ES6 JavaScript code into widely compatible ES5, ensuring broader browser support and execution in older environments. Developers relying on Babel to streamline their workflow will find the core functionality unchanged: seamless transformation of next-generation JavaScript features into readily usable code, complete with source map generation for simplified debugging. Key features like support for JSX syntax, ES6 modules, and various ES7 proposals continue to be supported.
The primary difference between versions 4.6.3 and 4.6.4 lies in an updated dependency: regexpu. Version 4.6.4 utilizes regexpu version ^1.1.2, while 4.6.3 depended on version ^1.1.1. While seemingly minor, this dependency update likely incorporates bug fixes, performance enhancements, or improved Unicode support within regular expression parsing, benefiting developers utilizing advanced regular expression features in their ES6 code. The release date also provides helpful context. Version 4.6.4 came out a day after 4.6.3, suggesting that the changes from version 4.6.3 were important but not considerable. Developers encountering issues related to regular expression handling or seeking the most up-to-date regular expression capabilities within their transpiled code should consider upgrading to version 4.6.4. For those with stable projects already using 4.6.3 and not experiencing such issues, the upgrade may be less critical, but still recommended for security reasons and access to the latest fixes.
All the vulnerabilities related to the version 4.6.4 of the package
Prototype Pollution in lodash
Versions of lodash
before 4.17.12 are vulnerable to Prototype Pollution. The function defaultsDeep
allows a malicious user to modify the prototype of Object
via {constructor: {prototype: {...}}}
causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.12 or later.
Prototype Pollution in lodash
Versions of lodash
before 4.17.5 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of Object
via __proto__
causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.5 or later.
Prototype Pollution in lodash
Versions of lodash
before 4.17.11 are vulnerable to prototype pollution.
The vulnerable functions are 'defaultsDeep', 'merge', and 'mergeWith' which allow a malicious user to modify the prototype of Object
via {constructor: {prototype: {...}}}
causing the addition or modification of an existing property that will exist on all objects.
Update to version 4.17.11 or later.
Regular Expression Denial of Service (ReDoS) in lodash
lodash prior to 4.7.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.7.11.
Prototype Pollution in lodash
Versions of lodash prior to 4.17.19 are vulnerable to Prototype Pollution. The functions pick
, set
, setWith
, update
, updateWith
, and zipObjectDeep
allow a malicious user to modify the prototype of Object if the property identifiers are user-supplied. Being affected by this issue requires manipulating objects based on user-provided property values or arrays.
This vulnerability causes the addition or modification of an existing property that will exist on all objects and may lead to Denial of Service or Code Execution under specific circumstances.
Regular Expression Denial of Service (ReDoS) in lodash
All versions of package lodash prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber
, trim
and trimEnd
functions.
Steps to reproduce (provided by reporter Liyuan Chen):
var lo = require('lodash');
function build_blank(n) {
var ret = "1"
for (var i = 0; i < n; i++) {
ret += " "
}
return ret + "1";
}
var s = build_blank(50000) var time0 = Date.now();
lo.trim(s)
var time_cost0 = Date.now() - time0;
console.log("time_cost0: " + time_cost0);
var time1 = Date.now();
lo.toNumber(s) var time_cost1 = Date.now() - time1;
console.log("time_cost1: " + time_cost1);
var time2 = Date.now();
lo.trimEnd(s);
var time_cost2 = Date.now() - time2;
console.log("time_cost2: " + time_cost2);
Command Injection in lodash
lodash
versions prior to 4.17.21 are vulnerable to Command Injection via the template function.