Expect, a crucial assertion library for JavaScript testing, saw a minor update from version 22.1.0 to 22.2.0. Both versions maintain the same dependencies including jest-diff, ansi-styles, jest-get-type, jest-regex-util, and jest-matcher-utils, indicating no fundamental architectural changes. However, a key difference lies in the updated versions of jest-message-util and jest-matcher-utils. Version 22.2.0 upgrades these dependencies to their respective 22.2.0 versions, while version 22.1.0 relies on the older 22.1.0 versions. This suggests improvements and bug fixes in message formatting and matcher utilities implemented specifically for better clarity and efficiency.
For developers, this means potentially more informative and helpful error messages during test failures, and enhanced functionality within the custom matchers they might be building. While the core API of Expect likely remains unchanged, these dependency updates indicate refinements within the assertion reporting and matching mechanisms. The updated version was released on February 7, 2018, approximately three weeks after the previous release on January 15, 2018, indicating a relatively short cycle focused on incremental improvements. Developers should consider upgrading to version 22.2.0 to leverage these enhanced utilities, leading to a potentially smoother and more insightful testing experience. Check the changelogs of jest-message-util and jest-matcher-utils for detailed information to know what changed.
All the vulnerabilities related to the version 22.2.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.
