Babel-jest is a crucial Jest plugin that seamlessly integrates Babel into your testing workflow, enabling you to transform your code for compatibility during testing. Comparing versions 24.6.0 and 24.7.0, we see subtle but important updates primarily focused on dependency management within the Jest ecosystem. Version 24.7.0 upgrades its internal dependencies on @jest/types and @jest/transform to version 24.7.0, aligning with the core Jest version. This signifies a commitment to staying current with the latest Jest functionalities and bug fixes. While babel-preset-jest remains at version 24.6.0 in both releases, the core Babel dependency (@babel/core) remains compatible at "^7.1.0" in devDependencies and "^7.0.0" in peerDependencies, suggesting stability in Babel integration.
Developers upgrading from 24.6.0 should note the updated @jest/types and @jest/transform dependencies, ensuring their project's Jest-related packages are synchronized for optimal performance and to avoid potential compatibility issues. A slightly reduced unpacked size in v24.7.0 might hint at minor optimizations. The release date difference indicates active maintenance and responsiveness from the Jest team in addressing issues and providing timely updates. Utilizing babel-jest allows developers to leverage modern JavaScript features without compromising their testing environment, streamlining development and ensuring code reliability through comprehensive testing. Consider upgrading to version 24.7.0 for the latest Jest-related dependency alignment.
All the vulnerabilities related to the version 24.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.
