The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsUpgrade org.apache.camel:camel-atmosphere-websocket to version 4.14.9, 4.18.4, 4.22.0 or higher.
Affected versions of this package are vulnerable to External Control of Assumed-Immutable Web Parameter through WebsocketConstants and the AtmosphereWebsocketEndpointBuilderFactory/WebsocketProducer dispatch headers in the atmosphere-websocket producer. An attacker can redirect or suppress messages intended for connected WebSocket peers by sending crafted inbound HTTP headers that populate websocket.connectionKey.list or websocket.connectionKey and influence which client(s) receive the message. In routes that bridge an untrusted HTTP consumer into an atmosphere-websocket: producer, the producer accepts these header values from the inbound exchange and uses them to select the delivery target. This lets an external sender take over the dispatch decision, causing messages to be delivered to the wrong WebSocket connection or not delivered at all.
Workarounds
websocket.* dispatch headers at the trust boundary before the atmosphere-websocket: producer, for example with removeHeaders("websocket.*") between the HTTP consumer and the producer; this prevents an external sender from overriding websocket.connectionKey.list / websocket.connectionKey and hijacking recipient selection.atmosphere-websocket: producer unless you first remove the dispatch namespace; this prevents crafted inbound HTTP headers from redirecting or suppressing messages to connected WebSocket peers.