Hippo4j through 1.5.0 SSRF via clientAddress Parameter
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| opengoofy | hippo4j | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Opengoofy | Hippo4j |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.342% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Hippo4j through 1.5.0 contains a server-side request forgery vulnerability in four ThreadPoolController endpoints that fail to validate the clientAddress parameter. Authenticated attackers can supply arbitrary hostnames and ports to trigger outbound GET requests to internal networks and cloud metadata services. | |
| Title | Hippo4j through 1.5.0 SSRF via clientAddress Parameter | |
| First Time appeared |
Opengoofy
Opengoofy hippo4j |
|
| Weaknesses | CWE-918 | |
| CPEs | cpe:2.3:a:opengoofy:hippo4j:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Opengoofy
Opengoofy hippo4j |
|
| References |
|
|
| Metrics |
cvssV3_1
|