Webpack version 4.7.0 introduces several changes compared to its predecessor, version 4.6.0. While the core functionality remains consistent, developers should be aware of updates primarily within the development dependencies. One notable difference is the update of typescript from version 2.9.0-dev.20180412 to 2.9.0-dev.20180503. This indicates upgrades and potential bug fixes in TypeScript support for projects leveraging Webpack. The introduction of eslint-plugin-jest":"21.12.2 and the removal of testing tools (mocha":"^3.2.0","should":"^11.1.1,"mocha-lcov-reporter":"^1.0.0") hints towards a potential shift or refinement in the testing strategy used within the Webpack project. This does not necessarily imply any action required by developers using Webpack, but it may inform decisions about linting and testing configurations in their own projects. The distribution metadata also reveals minor differences, like an increase the fileCount from 314 to 315 and unpackedSize from 1121236 to 1138126, suggesting internal structural adjustments or the addition of new assets. The upgrade between this versions is fairly safe, but it is always a good practice to back up the project before upgrading any dependency. Overall, version 4.7.0 represents an incremental update, likely focused on internal improvements and dependency management.
All the vulnerabilities related to the version 4.7.0 of the package
Regular Expression Denial of Service (ReDoS) in micromatch
The NPM package micromatch prior to version 4.0.8 is vulnerable to Regular Expression Denial of Service (ReDoS). The vulnerability occurs in micromatch.braces() in index.js because the pattern .* will greedily match anything. By passing a malicious payload, the pattern matching will keep backtracking to the input while it doesn't find the closing bracket. As the input size increases, the consumption time will also increase until it causes the application to hang or slow down. There was a merged fix but further testing shows the issue persisted prior to https://github.com/micromatch/micromatch/pull/266. This issue should be mitigated by using a safe pattern that won't start backtracking the regular expression due to greedy matching.
Uncontrolled resource consumption in braces
The NPM package braces fails to limit the number of characters it can handle, which could lead to Memory Exhaustion. In lib/parse.js, if a malicious user sends "imbalanced braces" as input, the parsing will enter a loop, which will cause the program to start allocating heap memory without freeing it at any moment of the loop. Eventually, the JavaScript heap limit is reached, and the program will crash.
Regular Expression Denial of Service (ReDoS)
npm ssri 5.2.2-6.0.1 and 7.0.0-8.0.0, processes SRIs using a regular expression which is vulnerable to a denial of service. Malicious SRIs could take an extremely long time to process, leading to denial of service. This issue only affects consumers using the strict option.
Cross-Site Scripting in serialize-javascript
Versions of serialize-javascript prior to 2.1.1 are vulnerable to Cross-Site Scripting (XSS). The package fails to sanitize serialized regular expressions. This vulnerability does not affect Node.js applications.
Upgrade to version 2.1.1 or later.
Insecure serialization leading to RCE in serialize-javascript
serialize-javascript prior to 3.1.0 allows remote attackers to inject arbitrary code via the function "deleteFunctions" within "index.js".
An object such as {"foo": /1"/, "bar": "a\"@__R-<UID>-0__@"} was serialized as {"foo": /1"/, "bar": "a\/1"/}, which allows an attacker to escape the bar key. This requires the attacker to control the values of both foo and bar and guess the value of <UID>. The UID has a keyspace of approximately 4 billion making it a realistic network attack.
