fix(deps): update dependency axios to v1.8.2 [security] #1452
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.7.7
->1.8.2
GitHub Vulnerability Alerts
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:
In this example, the request is sent to
http://attacker.test/
instead of thebaseURL
. As a result, the domain owner ofattacker.test
would receive theX-API-KEY
included in the request headers.It is recommended that:
baseURL
is set, passing an absolute URL such ashttp://attacker.test/
toget()
should not ignorebaseURL
.baseURL
with 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:
Even though
baseURL
is set tohttp://localhost:10001/
, axios sends the request tohttp://localhost:10002/
.Impact
baseURL
and does not validate path parameters is affected by this issue.Release Notes
axios/axios (axios)
v1.8.2
Compare Source
Bug Fixes
Contributors to this release
v1.8.1
Compare Source
Bug Fixes
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
globalThis.TextEncoder
when available (#6634) (df956d1)Contributors to this release
1.7.7 (2024-08-31)
Bug Fixes
Contributors to this release
1.7.6 (2024-08-30)
Bug Fixes
Contributors to this release
1.7.5 (2024-08-23)
Bug Fixes
ReferenceError: navigator is not defined
for custom environments; (#6567) (fed1a4b)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
Contributors to this release
v1.7.9
Compare Source
Reverts
Contributors to this release
v1.7.8
Compare Source
Bug Fixes
globalThis.TextEncoder
when available (#6634) (df956d1)Contributors to this release
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.
Thanks for the PR!
Deployments, as required, will be available below:
Any successful deployments (not always required) will be available here
Please create PRs in draft mode. Mark as ready to enable:
After merge, new images are deployed in: