Expect version 22.4.0 introduces several dependency updates compared to the previous stable version, 22.3.0, marking subtle yet potentially impactful refinements for developers. A primary change lies in the updated "jest-diff" dependency, moving from "^22.1.0" to "^22.4.0." This upgrade likely brings enhancements in how Jest compares and visualizes differences between values, improving debugging and test failure analysis. Specifically Jest is the most used testing framework so a good expect package will improve the usability of this framework.
Furthermore, "jest-message-util" and "jest-matcher-utils" also see updates, shifting from "^22.2.0" to "^22.4.0." These updates likely contain improvements in error message formatting and the utility functions used within matchers, respectively. Developers can anticipate clearer and more informative error messages when tests fail, simplifying the process of identifying and fixing issues.
The "expect" package, crucial for writing robust and expressive tests within the Jest framework, exhibits an increase in "unpackedSize" from 534361 to 535270, a negligible change suggesting added features or refinements without major structural alterations. This increase of near 1KB should not be impactful to web performance. Released a week after the previous version, expect@22.4.0 represents an iterative improvement focusing on refining the developer experience through dependency upgrades within the broader Jest ecosystem. Developers should review the changelogs for jest-diff, jest-message-util, and jest-matcher-utils to understand the specific bug fixes and improvements integrated into this expect release.
All the vulnerabilities related to the version 22.4.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.
