Upstream information
Description
axios versions 0.31.0 before 0.33.0 and 1.15.0 before 1.18.0 fail to recognize 0.0.0.0 as a loopback address in shouldBypassProxy.js, allowing requests to 0.0.0.0 to bypass NO_PROXY rules. Attackers can supply 0.0.0.0 URLs to route requests through configured proxies, potentially exposing local services when the proxy can reach the destination.SUSE information
Overall state of this security issue: Pending
This issue is currently rated as having moderate severity.
| CVSS detail | SUSE |
|---|---|
| Base Score | 4 |
| Vector | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N |
| Attack Vector | Network |
| Attack Complexity | High |
| Privileges Required | None |
| User Interaction | None |
| Scope | Changed |
| Confidentiality Impact | Low |
| Integrity Impact | None |
| Availability Impact | None |
| CVSSv3 Version | 3.1 |
| CVSS detail | CNA (VulnCheck) | SUSE |
|---|---|---|
| Base Score | 6.9 | 6.3 |
| Vector | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N |
| Attack Vector | Network | Network |
| Attack Complexity | Low | Low |
| Attack Requirements | Present | Present |
| Privileges Required | None | None |
| User Interaction | None | None |
| Vulnerable System Confidentiality Impact | Low | Low |
| Vulnerable System Integrity Impact | None | None |
| Vulnerable System Availability Impact | None | None |
| Subsequent System Confidentiality Impact | High | Low |
| Subsequent System Integrity Impact | None | None |
| Subsequent System Availability Impact | None | None |
| CVSSv4 Version | 4.0 | 4.0 |
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.
| Product(s) | Source package | State |
|---|---|---|
| Products under general support and receiving all security fixes. | ||
| SUSE Linux Enterprise Module for SAP Applications 15 SP7 | trento-web | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP7 | trento-web | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.0 | trento-web | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | trento-web | Affected |
| openSUSE Leap 16.0 | trento-web | Affected |
| Products under Long Term Service Pack support and receiving important and critical security fixes. | ||
| SUSE Linux Enterprise Server for SAP Applications 15 SP6 | trento-web | Affected |
| Products past their end of life and not receiving proactive updates anymore. | ||
| SUSE Linux Enterprise Module for SAP Applications 15 SP3 | trento-web | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP4 | trento-web | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP5 | trento-web | Affected |
| SUSE Linux Enterprise Module for SAP Applications 15 SP6 | trento-web | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP3 | trento-web | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP4 | trento-web | Affected |
| SUSE Linux Enterprise Server for SAP Applications 15 SP5 | trento-web | Affected |
| Container Status | ||
| trento/trento-web | trento-web | Affected |
SUSE Timeline for this CVE
CVE page created: Wed Aug 5 11:42:13 2026CVE page last modified: Wed Aug 5 11:42:13 2026