Expect, a crucial assertion library within the Jest testing framework, saw a minor version bump from 22.0.3 to 22.0.5, introducing subtle yet significant changes for developers relying on its robust matching capabilities. Released on January 9th, 2018, version 22.0.5 incorporated updates to several dependencies. Specifically, jest-diff, jest-regex-util, and jest-matcher-utils were bumped from '^22.0.3' to '^22.0.5'. While this might seem incremental, these dependency upgrades typically include bug fixes, performance improvements, and potential enhancements to the assertion error messages and diffing algorithms. These updates collectively contribute to a smoother and more informative testing experience.
Conversely, version 22.0.3, released earlier on December 19th, 2017, utilized older versions of these utilities. Although both versions share core dependencies like ansi-styles, jest-get-type and jest-message-util keeping those dependencies fixed, the updated versions in 22.0.5 suggests a refined approach to diffing and matching within the expect library.
For developers, although the change may seem small and the versions seem very similar, it is worth upgrading to the latest version (22.0.5) to take advantage of any potential improvements in those core utilities, ensuring higher stability for the library especially if you are also upgrading Jest at the same time. Keep an eye for any upgrade notes for future version bumps.
All the vulnerabilities related to the version 22.0.5 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.
