Technical impact
A logic flaw in the CoAP consumer causes an internal error message to be sent back as the payload of a 5.00 Internal Server Error response. When a type conversion failure occurs after a route has completed, the exception message—containing class names, package names and often file paths or host names—becomes visible to a remote CoAP client. The vulnerability therefore allows sensitive deployment details to be disclosed to anyone able to trigger the error scenario.
Affected Systems
The Apache Software Foundation’s Apache Camel product is affected. Versions from 4.0.0 up to but not including 4.18.5 and from 4.19.0 up to but not including 4.22.2 are vulnerable. All prior 4.14.x and 4.15.x‑4.17.x releases, as well as 4.19.x‑4.21.x lines, are end‑of‑life and will not receive a fix.
Risk and Exploitability
Based on the description, the likely attack vector is a specially crafted CoAP request that causes a type conversion failure after the route has completed. The CVSS score of 5.3 reflects moderate severity. Because the endpoint error is generated only when a conversion failure occurs, an attacker must craft a CoAP request that leads to such a failure; success yields an error response exposing internal details. EPSS data is unavailable and the vulnerability is not listed in CISA KEV. However, the vulnerability’s nature and the potential to reveal system internals mean that it should be mitigated promptly. The fix introduces a muteException consumer option that defaults to true, silencing error payloads, so upgrading to a supported release eliminates the data leakage without configuration changes.