-
Notifications
You must be signed in to change notification settings - Fork 4
chore(deps): update dependency axios [security] #3900
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
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/npm-axios-vulnerability
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CVE-2026-44489 in axios - low severity
[Patch Bypass] Proxy-Authorization Header Injection via Prototype Pollution — Incomplete Null-Prototype Fix in Axios 1.15.2
Summary
The
Object.create(null)fix introduced in Axios 1.15.2 (GHSA-q8qp-cvcw-x6jj) protects the top-level config object from prototype pollution. However, nested objects created byutils.merge()(e.g.,config.proxy) are still constructed as plain{}withObject.prototypein their chain.The
setProxy()function atlib/adapters/http.js:209-223readsproxy.username,proxy.password, andproxy.authwithouthasOwnPropertychecks. WhenObject.prototype.usernameis polluted,setProxy()constructs aProxy-Authorizationheader with attacker-controlled credentials and injects it into every proxied HTTP request.Severity: Medium (CVSS 5.4)
Affected Versions: 1.15.2 (and potentially 1.15.1)
Vulnerable Component:
lib/adapters/http.js(setProxy()) +lib/utils.js(merge())CWE
CVSS 3.1
Score: 5.6 (Medium)
Vector:
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:Lconfig.proxy. Unlike GHSA-q8qp-cvcw-x6jj which affected all requests unconditionallyconfig.baseURLhijack)Why This Is Lower Severity Than GHSA-q8qp-cvcw-x6jj (7.4 High)
config.proxysetconfig.baseURLPPconfig.authPPAuthorizationto target serverProxy-Authorizationto proxyThis Is a Patch Bypass
This vulnerability bypasses the fix introduced in Axios 1.15.2 for GHSA-q8qp-cvcw-x6jj. The fix correctly uses
Object.create(null)for the config object, blocking direct prototype pollution onconfig.proxy,config.auth, etc.However, the fix is incomplete: when a user legitimately sets
config.proxy = { host: 'proxy.corp', port: 8080 }, themergeConfig()function passes this object throughutils.merge(), which creates a new plain{}object (lib/utils.js:406: const result = {};). This new object inherits fromObject.prototype, re-opening the prototype pollution attack surface on the nested proxy object.config(top-level)Object.create(null)config.proxy(nested)utils.merge()→const result = {}setProxy()readsproxy.username,proxy.authwithouthasOwnPropertyRoot Cause Analysis
Step 1:
utils.merge()creates plain{}for nested objectsFile:
lib/utils.js, line 406When
mergeConfig()processesconfig.proxy,getMergedValue()callsutils.merge(), which creates a plain{}for the nested object. This plain object inherits fromObject.prototype.Step 2:
setProxy()reads proxy properties withouthasOwnPropertyFile:
lib/adapters/http.js, lines 209-223Complete Attack Chain
Proof of Concept
Reproduction Environment
Reproduction Steps
Verified PoC Output
Confirming the Bypass Mechanism
Fix 2: Use null-prototype objects in
utils.merge()Fix 3 (Comprehensive): Apply null-prototype to all objects created by
getMergedValue()References
Details
Remediation Aikido suggests bumping this package to version 1.16.0 to resolve this issue
Reply
@AikidoSec ignore: [REASON]to ignore this issue.More info