Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreSpring Cloud Gateway's LocalResponseCache decides whether an upstream response may be stored by comparing each complete Cache-Control header value with the strings private and no-store, instead of parsing the comma-separated directives. A protected upstream response with a combined value, such as private, no-store or the Spring Security default no-cache, no-store, max-age=0, must-revalidate, is therefore stored in the route cache even though the upstream prohibited it. A later request can then be served that cached response without reaching the upstream, so an unauthenticated attacker can read content that was meant for an authenticated user.
Applications are affected only if LocalResponseCache is enabled on a route that forwards to an upstream that returns user-specific or otherwise private responses with a Cache-Control header containing more than one directive, and the upstream does not distinguish callers with a Vary header.
Spring Cloud Gateway:
| Fix version | Availability |
|---|---|
| 5.0.5 | OSS |
| 5.0.4.1 | Enterprise Support Only |
| 4.3.7 | Enterprise Support Only |
| 4.2.11 | Enterprise Support Only |
No further mitigation steps are necessary.
This vulnerability was discovered and responsibly reported by hussst and Yu Yicheng.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy