Expect, a crucial assertion library often used with Jest, saw a subtle refinement between version 22.0.0 and 22.0.1. Both versions maintain the same MIT license and are hosted within the Facebook Jest repository on GitHub, ensuring community-backed stability. The core dependencies remained largely the same, indicating no significant architectural changes. Notably, both versions depend on ansi-styles at version ^3.2.0 and jest-regex-util at ^21.2.0, suggesting a consistent approach to terminal styling and regular expression handling.
The crucial shift comes in the dependencies on other jest-* utilities. Version 22.0.1 updated its dependencies to their corresponding 22.0.1 versions, specifically jest-diff, jest-get-type, jest-message-util, and jest-matcher-utils. This suggests internal bug fixes or incremental improvements within those related modules, promoting smoother integration and potentially fixing edge-case issues discovered in version 22.0.0. Developers considering an upgrade can anticipate improved stability and potentially more accurate error messages. The release dates highlight a gap of roughly 9 hours between versions, potentially reflecting a hotfix or a small but vital patch after the initial 22.0.0 release. Check the Jest changelog for detailed accounts of the fixes bundled within the new library to assess whether the improvements are relevant in your context.
All the vulnerabilities related to the version 22.0.1 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.
