Babel-jest 24.8.0 introduces subtle but important updates for developers leveraging Jest with Babel for JavaScript transformation. The primary difference from version 24.7.1 lies in its dependency updates within the Jest ecosystem. Specifically, @jest/types progresses from version 24.7.0 to 24.8.0, and @jest/transform moves from 24.7.1 to 24.8.0. These updates likely encompass bug fixes, performance enhancements, and potentially new features within Jest's typing and transformation pipeline, crucial for a smooth testing experience.
Developers should evaluate these updated dependencies for compatibility within their existing Jest configurations. While babel-jest itself remains largely consistent in its core functionality – providing a bridge between Jest and Babel – these underlying dependency upgrades can impact the behavior of tests, especially those relying on intricate type definitions or custom transformations managed by Jest. The release date of 24.8.0 is May 5th, 2019, suggesting a period of potential refinement and bug fixing following the earlier 24.7.1 release in April 2019. It's recommended to review the changelogs for @jest/types and @jest/transform to understand the precise nature of the changes introduced and their potential effect on your projects.
All the vulnerabilities related to the version 24.8.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.
