Ts-loader versions 5.3.2 and 5.3.1, both TypeScript loaders for webpack, share a common foundation with dependencies like chalk, semver, micromatch, loader-utils, and enhanced-resolve for core functionality. Developers upgrading should review the changes, focusing on updated tools and potential breaking changes.
While the core dependencies remain consistent, the devDependencies showcase some differences. Karma-jasmine gets updated in version 5.3.2 to version "^2.0.0" from "1.0.0" in version 5.3.1, karma-webpack gets updated to version "^4.0.0-rc.5" from "2.0.6". This could imply changes or bugfixes in the test suite. The size of the package increased from 323366 to 355044. Both versions peer depend on typescript "*" so should work with any version of typescript.
These updates likely contain bug fixes, performance enhancements, and compatibility adjustments for a smoother development experience. Reviewing the changelog or release notes associated with these specific updates is highly recommended to understand the precise implications and ensure a seamless transition. Developers should examine the impact of the karma-jasmine and karma-webpack updates on their testing configurations.
All the vulnerabilities related to the version 5.3.2 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.
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.
