Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreSpring Cloud Gateway's WebsocketRoutingFilter accepts WebSocket handshakes without checking the Origin header. Browsers do not apply the same-origin policy or CORS to WebSocket handshakes. They only send the Origin header and rely on the server to accept or reject the request. Because the gateway does not reject cross-origin handshakes by default, a malicious web page can cause a victim's browser to open a WebSocket connection through the gateway to a backend service, using any credentials the browser attaches automatically, such as cookies.
Applications are affected only if they expose a route with a ws or wss URI through the gateway. Spring Cloud Gateway now rejects cross-origin WebSocket handshakes by default with a 403 Forbidden response, and provides the spring.cloud.gateway.server.webflux.websocket.allowed-origins and spring.cloud.gateway.server.webflux.websocket.allowed-origin-patterns properties (spring.cloud.gateway.websocket.* for the 4.x and 3.1.x lines) to allow specific origins.
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 |
| 3.1.15 | Enterprise Support Only |
No further mitigation steps are necessary.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy