Expect version 22.0.6 represents a minor update to the popular assertion library for JavaScript testing, building upon the foundation established by version 22.0.5. Both versions, licensed under MIT, are integral parts of the Jest testing framework ecosystem, maintained within the Facebook/Jest repository. The core function of Expect remains consistent: providing a rich set of matchers for making assertions about expected outcomes in tests, aiding developers in writing clear and reliable test suites.
Key differences between the versions lie primarily in their dependency updates. Expect 22.0.6 upgrades several internal Jest-related packages to their corresponding 22.0.6 versions. Notably, jest-diff, a crucial component for displaying readable diffs during assertion failures, jest-regex-util, and jest-matcher-utils are updated. jest-get-type also receives an update going from version 22.0.3 to 22.0.6, along with jest-message-util that jumps from 22.0.3 to 22.0.6. These updates likely incorporate bug fixes, performance improvements, or enhancements to the diffing and matching logic.
Developers upgrading to 22.0.6 can expect improved consistency and reliability within the Jest testing experience. The updated dependencies ensure that Expect leverages the latest improvements in diffing algorithms, regex handling, and utility functions, potentially leading to more accurate and informative test failure messages. While the core API remains largely unchanged, the underlying enhancements contribute to a more robust and developer-friendly testing environment. The release date difference also suggests relatively quick turnaround for the fix, meaning that the identified issues of the previous version were quite important.
All the vulnerabilities related to the version 22.0.6 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.
