request-filtering-agent before 3.2.2 SSRF Filter Bypass via IPv4-Compatible IPv6 Addresses
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| azu | request-filtering-agent | unaffected |
|
No data.
No data.
No data available yet.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
No EPSS score available.
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Description | request-filtering-agent before 3.2.2 contains a server-side request forgery filter bypass because address validation in src/request-filtering-agent.ts treats IPv4-compatible IPv6 addresses in the ::/96 range as public unicast. Attackers controlling a fetched URL can use addresses like ::7f00:1 or ::a9fe:a9fe to reach loopback or link-local services, including cloud metadata endpoints. | |
| Title | request-filtering-agent before 3.2.2 SSRF Filter Bypass via IPv4-Compatible IPv6 Addresses | |
| Weaknesses | CWE-918 | |
| References |
|
|
| Metrics |
cvssV3_1
|
No data.
Server-Side Request Forgery (SSRF)
No data.
No data.
No data.
No data.