Micromatch version 2.3.11 is a minor update to the glob matching library, following closely after version 2.3.10. Both versions aim to provide a faster and more efficient alternative to minimatch and multimatch for JavaScript and Node.js environments. The core functionality, centered around glob pattern matching, remains consistent between the two releases. Developers can expect similar performance and behavior in terms of matching files and strings against glob patterns, making it ideal for tasks like file system traversal, build automation, and code analysis.
A key aspect for developers is the stability of the dependencies; they are identical. This means a smoother upgrade path for those already using micromatch. The dependency list, featuring packages like braces, extglob, and is-glob, confirms the library's robust approach to handling complex glob patterns. The devDependencies section contains tools useful to contribute to the library or run tests but do not affect usage as a dependency. The upgrade between versions is simple as no code changes are to be expected related to the upgrade.
Looking at the releaseDate, version 2.3.11 was published on July 15, 2016, while 2.3.10 was published on June 21, 2016. The tight release window suggests that version 2.3.11 likely contains bug fixes, performance improvements, or minor tweaks discovered shortly after the release of 2.3.10. While the changes might not be immediately apparent from the metadata, upgrading is still advisable to benefit from the latest refinements and ensure greater stability.
All the vulnerabilities related to the version 2.3.11 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.
