Spring WS SSRF via unvalidated WS-Addressing reply destinations
Spring Web Services
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.ws:spring-ws-core Maven |
|
|
Spring Web Services
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.ws:spring-ws-core Maven |
|
|
When WS-Addressing is used with non-anonymous ReplyTo or FaultTo addresses, Spring WS may initiate outbound connections through configured WebServiceMessageSender instances to destinations taken directly from request headers without verifying that those destinations are safe to connect to.
Affected versions: Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.
From the CVE record · vmware
When WS-Addressing uses non-anonymous ReplyTo or FaultTo addresses, Spring Web Services may connect to destinations supplied in request headers without checking whether they are safe. An attacker who can supply those headers may cause outbound connections through configured WebServiceMessageSender instances.
Teams running Spring Web Services or Maven package org.springframework.ws:spring-ws-core versions 5.0.0–5.0.1, 4.1.0–4.1.3, 4.0.0–4.0.18, or 3.1.0–3.1.8 should check their deployments.