http-proxy-middleware is a lightweight and versatile Node.js proxy middleware designed for Connect, Express, and BrowserSync environments, simplifying the process of routing client requests to backend servers. Comparing versions 0.15.0 and 0.15.1, the core functionalities remain largely consistent. Both versions offer the same key dependencies, including lodash for utility functions, is-glob for simplified globbing, http-proxy for the core proxying mechanism, and micromatch for advanced pattern matching in route targeting. The development dependencies, vital for testing and development, such as ws, opn, chai, mocha, connect, express, istanbul, coveralls, browser-sync, istanbul-coveralls, and mocha-lcov-reporter, are also identical between the two versions, indicating a focus on maintaining a stable development environment.
The primary distinction lies in the release date, with version 0.15.1 being released on May 26, 2016, subsequent to version 0.15.0, which was released on May 3, 2016. Typically, such a minor version bump (0.15.0 to 0.15.1) suggests bug fixes, minor enhancements, or dependency updates that don't introduce breaking changes. Developers can generally migrate between these versions without significant code modifications. While a detailed changelog would offer precise insights, the upgrade to 0.15.1 likely incorporates improvements that enhance stability or resolve minor issues, making it the recommended version for new projects and updates to existing implementations. The MIT license ensures flexibility and ease of integration into a wide array of projects.
All the vulnerabilities related to the version 0.15.1 of the package
Denial of service in http-proxy-middleware
Versions of the package http-proxy-middleware before 2.0.7, from 3.0.0 and before 3.0.3 are vulnerable to Denial of Service (DoS) due to an UnhandledPromiseRejection error thrown by micromatch. An attacker could kill the Node.js process and crash the server by making requests to certain paths.
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.
