Severity:
CVSS 3.1: 5.3 (medium) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Affected versions:
- Apache Camel (org.apache.camel:camel-coap) 4.0.0 before 4.18.5
- Apache Camel (org.apache.camel:camel-coap) 4.19.0 before 4.22.2
Description:
Generation of Error Message Containing Sensitive Information vulnerability in
Apache Camel CoAP component.
This issue affects Apache Camel: from 4.0.0 before 4.18.5, from 4.19.0 before
4.22.2.
When the CoAP consumer could not build its response once the route had
completed, CamelCoapResource caught the resulting exception and sent its
message back to the CoAP client as the payload of a 5.00 Internal Server Error
response. The typical case is a type conversion failure: the consumer converts
the final message body to the byte[] payload, and the CamelCoapMaxAge and
CamelCoapETag headers to their types, after the route has returned, and
therefore outside the route's error handler. On the affected releases the
message of such a failure names the class of the value being converted, carries
the value's string form, and ends with the class name and message of the
underlying cause, so a remote CoAP client could read internal detail about the
deployment: class and package names, the string form of the value, such as the
path of a file body, and whatever the cause carries, which in practice can
include paths, host names and connection detail of a backend. The consumer had
no option to suppress this, unlike the HTTP consumers, which offer a
muteException option for that purpose. The exception raised by a failing route
was not sent: the consumer did not check whether the exchange had failed, and
answered a route failure with 2.05 Content and whatever body the message held
at that point. Reaching the disclosure therefore requires a route whose
completed response a remote client can make unconvertible, which depends on how
the route is written.
Users are recommended to upgrade to version 4.23.0, which fixes the issue. If
users are on the 4.22.x releases stream, then they are suggested to upgrade to
4.22.2. If users are on the 4.18.x releases stream, then they are suggested to
upgrade to 4.18.5. The 4.14.x releases stream and earlier, and the 4.15.x to
4.17.x and 4.19.x to 4.21.x release lines, reached end of life before this
issue was resolved and will not receive a fix, so deployments on them must move
to a supported release. The upgrade is enough on its own: the new muteException
consumer option defaults to true on all three fixed release lines, so the error
response carries no payload without any configuration change. For deployments
that cannot upgrade immediately, make sure the response can always be built
once the route has completed: convert the body to byte[] or String as the last
step of each route that consumes from a coap endpoint, for example with
convertBodyTo, give the CamelCoapMaxAge and CamelCoapETag headers only values
of their own types, and add an onException handler that marks the failure as
handled and sets the response body explicitly, so that a conversion failure is
raised and replaced inside the route rather than in the consumer.
Solution:
Users are recommended to upgrade to version 4.23.0, which fixes the issue. If
users are on the 4.22.x releases stream, then they are suggested to upgrade to
4.22.2. If users are on the 4.18.x releases stream, then they are suggested to
upgrade to 4.18.5. The fix adds a muteException consumer option to the coap,
coaps, coap+tcp and coaps+tcp endpoints, defaulting to true on all three
release lines, so the upgrade is enough on its own and the error response
carries no payload without any configuration change. An exception raised while
the response is built is answered with an empty 5.00 Internal Server Error and
reported through the consumer's exception handler, and a failed exchange,
previously answered with 2.05 Content and the body the message held when the
route failed, is now answered with 5.00 Internal Server Error under the same
rule. Setting muteException=false sends the exception's message as the payload
of the 5.00 response, for a route failure as well. The 4.14.x releases stream
and earlier, and the 4.15.x to 4.17.x and 4.19.x to 4.21.x release lines,
reached end of life before this issue was resolved and will not receive a fix,
so deployments on them must move to a supported release.
Work Arounds:
For deployments that cannot upgrade immediately, make sure the response can
always be built once the route has completed: convert the body to byte[] or
String as the last step of each route that consumes from a coap endpoint, for
example with convertBodyTo, give the CamelCoapMaxAge and CamelCoapETag headers
only values of their own types, and add an onException handler that marks the
failure as handled and sets the response body explicitly, so that a conversion
failure is raised and replaced inside the route rather than in the consumer.
Credit:
Zhixi "Jace" Sun, independent security researcher (finder)
Andrea Cosentino (remediation developer)
References:
https://camel.apache.org/security/CVE-2026-101259.html
https://issues.apache.org/jira/browse/CAMEL-25087
https://github.com/apache/camel/pull/26994
https://github.com/apache/camel/pull/27046
https://github.com/apache/camel/pull/27048
https://camel.apache.org/security/CVE-2026-84180.html
https://camel.apache.org/security/CVE-2026-85246.html
https://camel.apache.org/security/CVE-2026-85257.html
https://camel.apache.org/security/CVE-2026-85315.html
https://camel.apache.org/
https://www.cve.org/CVERecord?id=CVE-2026-101259
