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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Attack Requirements
None
No additional conditions
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v4.0
Weakness Type (CWE)
References 5
https://github.com/opengoofy/hippo4j
disclosure@vulncheck.com
https://github.com/opengoofy/hippo4j/blob/73124de92e269940bdf44f4534b37a13a36ff…
disclosure@vulncheck.com
https://github.com/opengoofy/hippo4j/blob/73124de92e269940bdf44f4534b37a13a36ff…
disclosure@vulncheck.com
https://github.com/opengoofy/hippo4j/issues/1621
disclosure@vulncheck.com
https://www.vulncheck.com/advisories/hippo4j-through-1.5.0-ssrf-via-clientaddre…
disclosure@vulncheck.com