Expect, a core assertion library within the Jest testing framework, saw a significant version jump from 21.2.1 to 22.0.0, released on December 18, 2017, after version 21.2.1 released on September 27, 2017. While both versions maintain the MIT license and reside within the Facebook Jest repository, the version 22.0.0 introduces updated dependencies, reflecting improvements and bug fixes within the broader Jest ecosystem. Developers upgrading should pay close attention to the peer dependency upgrades.
Key differences lie in the updated versions of its dependencies. For instance, jest-diff jumps from ^21.2.1 to ^22.0.0, jest-get-type moves from ^21.2.0 to ^22.0.0, and jest-message-util and jest-matcher-utils both shift from ^21.2.1 to ^22.0.0. These upgrades likely incorporate enhanced error messages, improved type checking, and better utility functions for writing custom matchers. While ansi-styles and jest-regex-util remains the same. Developers should consult the Jest changelog for detailed information on the specific changes and bug fixes included in these dependency updates, ensuring compatibility and leveraging the latest features for writing robust and expressive tests. The updated release demonstrates active maintenance and integration within the Jest project.
All the vulnerabilities related to the version 22.0.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.
Regular Expression Denial of Service (ReDoS) in braces
A vulnerability was found in Braces versions prior to 2.3.1. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.
Regular Expression Denial of Service in braces
Versions of braces prior to 2.3.1 are vulnerable to Regular Expression Denial of Service (ReDoS). Untrusted input may cause catastrophic backtracking while matching regular expressions. This can cause the application to be unresponsive leading to Denial of Service.
Upgrade to version 2.3.1 or higher.
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.
