[APS-18718] fix: update axios to ^1.15.0 to resolve SSRF via NO_PROXY bypass#1079
Open
avinash-bharti wants to merge 1 commit intomasterfrom
Open
[APS-18718] fix: update axios to ^1.15.0 to resolve SSRF via NO_PROXY bypass#1079avinash-bharti wants to merge 1 commit intomasterfrom
avinash-bharti wants to merge 1 commit intomasterfrom
Conversation
…s [APS-18718] - Bump axios from ^1.7.7 to ^1.15.0 - Fixes CVE-2025-62718 / GHSA-3p68-rc4w-qgx5 - Axios did not normalize hostnames when checking NO_PROXY rules, allowing requests to loopback addresses (localhost., [::1]) to bypass NO_PROXY and go through the configured proxy (SSRF risk) Resolves: APS-18718
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Security Fix: APS-18718
Issue
Axios has a NO_PROXY Hostname Normalization Bypass that leads to SSRF (CVE-2025-62718 / GHSA-3p68-rc4w-qgx5).
Axios does not correctly handle hostname normalization when checking
NO_PROXYrules. Requests to loopback addresses likelocalhost.(with a trailing dot) or[::1](IPv6 literal) skipNO_PROXYmatching and go through the configured proxy. This allows attackers to force requests through a proxy even ifNO_PROXYis set up to protect loopback or internal services, leading to potential SSRF.Root Cause
Axios performs a literal string comparison instead of normalizing hostnames before checking
NO_PROXY. Per RFC 1034 and RFC 3986,localhost.(with trailing dot) is equivalent tolocalhostat the DNS level, and[::1]is the IPv6 loopback. Axios fails to normalize these before matching, causing requests to bypassNO_PROXYrules.Fix Applied
axiosdependency inpackage.jsonfrom^1.7.7to^1.15.0NO_PROXYevaluationTesting
npm test) -- automated execution was blocked in this sessionbrowserstack-cypress runwith valid credentials to confirm the CLI still works end-to-end after the axios bumpBrowserStack Session Sanity (mandatory for session repos):
Manual testing steps:
git checkout fix/APS-18718-update-axios-ssrfnpm installto resolve the updated axios versionnpm testto verify unit tests passbrowserstack-cypress run --username $BROWSERSTACK_USERNAME --key $BROWSERSTACK_ACCESS_KEYRisk Assessment
Jira Ticket
https://browserstack.atlassian.net/browse/APS-18718
Advisory
GHSA-3p68-rc4w-qgx5
Checklist