CyberRota Analysis
AI-GeneratedEclipse KUKSA Databroker version 0.6.1 is vulnerable due to a failure in the kuksa.val.v2.VAL/PublishValue gRPC handler to validate the optional data_point field in PublishValueRequest, leading to a panic in the Tokio worker thread when the field is omitted. This vulnerability can be exploited by any client with a valid JWT token, potentially disrupting individual gRPC calls without affecting the overall service availability. Organizations using this version of KUKSA Databroker should prioritize patching to mitigate the risk of service disruption.
Original NVD Description
In Eclipse KUKSA Databroker version 0.6.1, the kuksa.val.v2.VAL/PublishValue gRPC handler fails to validate the existence of the optional data_point field in PublishValueRequest. When a request contains a valid signal_id but omits data_point, the server directly calls unwrap() on request.data_point, triggering a panic in the Tokio worker thread. This issue can be triggered by any client holding a valid JWT token. Unauthenticated or invalid-token requests are rejected and do not reach the vulnerable path. The panic causes the individual gRPC call to be cancelled but does not terminate the Databroker process, which remains available for subsequent requests.
Related CVEs
Other vulnerabilities affecting the same vendor(s)