CyberRota Analysis
AI-GeneratedVersions of axios between 1.15.2 and 1.18.0 are vulnerable to prototype-pollution read-side gadgets, which can lead to outbound request tampering when an application uses a custom auth object that lacks username and/or password properties. This vulnerability allows an attacker to inject malicious Basic auth credentials into the Authorization header, potentially compromising sensitive information if certain application-specific conditions are met. Developers and security teams using affected axios versions should prioritize remediation to mitigate the risk of unauthorized access and credential disclosure.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
axios versions >=1.15.2 and <1.18.0 contain prototype-pollution read-side gadgets in Basic auth subfield handling (lib/adapters/http.js and lib/helpers/resolveConfig.js). When an application is already affected by a separate prototype-pollution primitive and makes an axios request with an own auth object that omits the username and/or password properties, axios reads the inherited Object.prototype.username and Object.prototype.password values and uses them to construct an outbound 'Authorization: Basic ...' header. axios itself does not pollute prototypes. The practical impact is outbound request tampering: an attacker who controls the polluted prototype values can inject attacker-chosen Basic auth credentials or replace an existing Authorization header. Credential disclosure is only possible under additional application-specific conditions.