org.apache.camel:camel-vertx-websocket 4.15.0

Direct Vulnerabilities

Known vulnerabilities in the org.apache.camel:camel-vertx-websocket package. This does not include vulnerabilities belonging to this package’s dependencies.

Fix vulnerabilities automatically

Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

Fix for free

Vulnerability	Vulnerable Version
M Server-side Request Forgery (SSRF) Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the `VertxWebsocketConsumer` inbound header mapping in `components/camel-vertx/camel-vertx-websocket`. An attacker can redirect server-side HTTP requests and disclose sensitive values by sending WebSocket query or path parameters named like Camel control headers, such as `CamelHttpUri`, to an exposed WebSocket endpoint. The consumer copied those externally supplied parameters into the Camel `Exchange` header map without filtering the Camel header namespace, so a downstream HTTP producer could be driven to an attacker-chosen URI and resolve attacker-controlled placeholders. In routes that bridge the WebSocket consumer into HTTP, this exposes internal services, metadata endpoints, environment variables, application properties, and vault secrets to an unauthenticated remote client. How to fix Server-side Request Forgery (SSRF)? Upgrade `org.apache.camel:camel-vertx-websocket` to version 4.14.8, 4.18.3, 4.21.0 or higher.	[,4.14.8)[4.15.0,4.18.3)[4.19.0,4.21.0)
M Server-side Request Forgery (SSRF) Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the `WebsocketConsumer.service` process. An attacker can redirect server-side HTTP requests to arbitrary destinations and access sensitive environment variables, application properties, or vault secrets by injecting specially crafted WebSocket query parameters that are mapped into internal headers. This is only exploitable if the WebSocket endpoint is exposed without authentication and is bridged directly into an HTTP producer whose target URI can be influenced from message headers. How to fix Server-side Request Forgery (SSRF)? Upgrade `org.apache.camel:camel-vertx-websocket` to version 4.14.8, 4.18.3, 4.21.0 or higher.	[,4.14.8)[4.15.0,4.18.3)[4.19.0,4.21.0)

Vulnerability

Vulnerable Version

Server-side Request Forgery (SSRF)

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the VertxWebsocketConsumer inbound header mapping in components/camel-vertx/camel-vertx-websocket. An attacker can redirect server-side HTTP requests and disclose sensitive values by sending WebSocket query or path parameters named like Camel control headers, such as CamelHttpUri, to an exposed WebSocket endpoint. The consumer copied those externally supplied parameters into the Camel Exchange header map without filtering the Camel header namespace, so a downstream HTTP producer could be driven to an attacker-chosen URI and resolve attacker-controlled placeholders. In routes that bridge the WebSocket consumer into HTTP, this exposes internal services, metadata endpoints, environment variables, application properties, and vault secrets to an unauthenticated remote client.

How to fix Server-side Request Forgery (SSRF)?

Upgrade org.apache.camel:camel-vertx-websocket to version 4.14.8, 4.18.3, 4.21.0 or higher.

[,4.14.8)[4.15.0,4.18.3)[4.19.0,4.21.0)

Server-side Request Forgery (SSRF)

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the WebsocketConsumer.service process. An attacker can redirect server-side HTTP requests to arbitrary destinations and access sensitive environment variables, application properties, or vault secrets by injecting specially crafted WebSocket query parameters that are mapped into internal headers. This is only exploitable if the WebSocket endpoint is exposed without authentication and is bridged directly into an HTTP producer whose target URI can be influenced from message headers.

How to fix Server-side Request Forgery (SSRF)?

Upgrade org.apache.camel:camel-vertx-websocket to version 4.14.8, 4.18.3, 4.21.0 or higher.

[,4.14.8)[4.15.0,4.18.3)[4.19.0,4.21.0)

org.apache.camel:camel-vertx-websocket@4.15.0

latest version

latest non vulnerable version

first published

latest version published

licenses detected

package registry

Direct Vulnerabilities

Fix vulnerabilities automatically