Ts-loader is a TypeScript loader for webpack, enabling developers to seamlessly integrate TypeScript code into their webpack-based projects. Comparing versions 5.3.3 and 5.3.2 reveals subtle yet important updates. Both versions share the same core dependencies: chalk, semver, micromatch, loader-utils, and enhanced-resolve ensuring consistent handling of console output, version comparison, globbing patterns, webpack loader utilities and module resolution. The development dependencies, essential for building and testing the package, also remain identical across both versions. This shared foundation ensures that the developer experience for tasks like linting, testing (using Karma and Mocha), and webpack integration stays consistent.
The changes between the two versions are subtle. Version 5.3.3 has a fileCount of 38 while version 5.3.2 has 37. Unpacked size of the newer package increased from 355044 to 355308. Ts-loader lets you leverage the power of TypeScript's static typing and ESNext features within your webpack workflow without extra effort. Ts-loader simplifies the integration of Typescript into modern web development projects and is critical for developers using Webpack and Typescript together.
All the vulnerabilities related to the version 5.3.3 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.
