Forwarded header exploit with Spring HATEOAS on WebFlux
Spring HATEOAS
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.hateoas:spring-hateoas Maven |
|
|
Spring HATEOAS
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.hateoas:spring-hateoas Maven |
|
|
Reactive web applications that use Spring HATEOAS to produce hypermedia-based responses might be exposed to malicious forwarded headers if they are not behind a trusted proxy that ensures correctness of such headers, or if they don't have anything else in place to handle (and possibly discard) forwarded headers either in WebFlux or at the level of the underlying HTTP server.
For the application to be affected, it needs to satisfy the following requirements:
* It needs to use the reactive web stack (Spring WebFlux) and Spring HATEOAS to create links in hypermedia-based responses. * The application infrastructure does not guard against clients submitting (X-)Forwarded… headers.
From the CVE record · vmware
Spring WebFlux applications that use Spring HATEOAS to create links in hypermedia responses may be vulnerable to malicious forwarded headers. Clients can submit those headers and affect generated links when the application infrastructure does not guard against them. The input does not specify authentication requirements or user interaction.
Check applications using Maven org.springframework.hateoas:spring-hateoas versions below 1.5.5, 2.0.0 through 2.0.4, or 2.1.0 that generate hypermedia links with Spring WebFlux.