This is an automated email from the ASF dual-hosted git repository. oscerd pushed a commit to branch main in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit 6a8ebdaf59b72e9cc24f54a0cd2c18e902a8364f Author: Andrea Cosentino <[email protected]> AuthorDate: Fri Sep 4 09:09:41 2026 +0200 Added CVE-2026-84180 Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Claude-Session: https://claude.ai/code/session_013qz9ir11vuQYfQApzwHAHD Signed-off-by: Andrea Cosentino <[email protected]> --- content/security/CVE-2026-84180.md | 21 ++++++++++++++++++++ content/security/CVE-2026-84180.txt.asc | 35 +++++++++++++++++++++++++++++++++ 2 files changed, 56 insertions(+) diff --git a/content/security/CVE-2026-84180.md b/content/security/CVE-2026-84180.md new file mode 100644 index 00000000..e82f4264 --- /dev/null +++ b/content/security/CVE-2026-84180.md @@ -0,0 +1,21 @@ +--- +title: "Apache Camel Security Advisory - CVE-2026-84180" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-84180.html +draft: false +type: security-advisory +cve: CVE-2026-84180 +severity: MEDIUM +summary: "Camel-Knative: information disclosure - a route failure was written back to the remote caller as the response body, so the exception class, message and stack trace of an internal error reached an external sender" +description: "When processing of an exchange failed on the consumer side, the Knative HTTP consumer wrote the resulting exception back to the remote caller as the response body, including its class name, message and stack trace. An external sender could therefore provoke a failure and read internal detail about the deployment: class and package names, file system or host names carried in exception messages, and the shape of the route. That detail is useful for building a more targeted at [...] +mitigation: "Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The consumer now honours a muteException option that defaults to true, so a route failure returns an empty body with the error status rather than the exception. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, add an onException handler [...] +credit: "This issue was discovered by Claude Security Scan Tool" +affected: "From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1." +fixed: 4.18.5, 4.22.1 and 4.23.0 +--- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24428 refers to the various commits that resolved the issue, and has more details. + +The fix was merged on main in https://github.com/apache/camel/pull/25685 (commit 22cccdecdebd948bea1bcdd6a184345d013a3b1a), backported to camel-4.22.x in https://github.com/apache/camel/pull/25835 (commit ca9f326ada9703d32badabad2f32c66886ffa470) and to camel-4.18.x in https://github.com/apache/camel/pull/25836 (commit 51e3f9047693120b4dd086dcceba16356f92e0aa). + +The issue is classified as CWE-209 Generation of Error Message Containing Sensitive Information. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later. diff --git a/content/security/CVE-2026-84180.txt.asc b/content/security/CVE-2026-84180.txt.asc new file mode 100644 index 00000000..183e38e6 --- /dev/null +++ b/content/security/CVE-2026-84180.txt.asc @@ -0,0 +1,35 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +- --- +title: "Apache Camel Security Advisory - CVE-2026-84180" +date: 2026-08-31T10:00:00+02:00 +url: /security/CVE-2026-84180.html +draft: false +type: security-advisory +cve: CVE-2026-84180 +severity: MEDIUM +summary: "Camel-Knative: information disclosure - a route failure was written back to the remote caller as the response body, so the exception class, message and stack trace of an internal error reached an external sender" +description: "When processing of an exchange failed on the consumer side, the Knative HTTP consumer wrote the resulting exception back to the remote caller as the response body, including its class name, message and stack trace. An external sender could therefore provoke a failure and read internal detail about the deployment: class and package names, file system or host names carried in exception messages, and the shape of the route. That detail is useful for building a more targeted at [...] +mitigation: "Upgrade to Apache Camel 4.23.0, which fixes the issue. Users on the 4.18.x LTS releases stream should upgrade to 4.18.5. Users on the 4.22.x LTS releases stream should upgrade to 4.22.1. The consumer now honours a muteException option that defaults to true, so a route failure returns an empty body with the error status rather than the exception. Set muteException=false to restore the previous output. For deployments that cannot upgrade immediately, add an onException handler [...] +credit: "This issue was discovered by Claude Security Scan Tool" +affected: "From 4.0.0 before 4.18.5, from 4.19.0 before 4.22.1." +fixed: 4.18.5, 4.22.1 and 4.23.0 +- --- + +The JIRA ticket: https://issues.apache.org/jira/browse/CAMEL-24428 refers to the various commits that resolved the issue, and has more details. + +The fix was merged on main in https://github.com/apache/camel/pull/25685 (commit 22cccdecdebd948bea1bcdd6a184345d013a3b1a), backported to camel-4.22.x in https://github.com/apache/camel/pull/25835 (commit ca9f326ada9703d32badabad2f32c66886ffa470) and to camel-4.18.x in https://github.com/apache/camel/pull/25836 (commit 51e3f9047693120b4dd086dcceba16356f92e0aa). + +The issue is classified as CWE-209 Generation of Error Message Containing Sensitive Information. The camel-4.14.x line reached end of life before this fix and does not receive it; deployments on 4.14.x should move to 4.18.5 or later. +-----BEGIN PGP SIGNATURE----- + +iQEzBAEBCgAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmqabrUACgkQ406fOAL/ +QQArfggAruQhAary7elqu01648s4ZNfyp+84N4qJ/MM1wkdWKX21oBeVerU0u0iV +tEaJ7Cq11gO4vc0v5U9bnx+L67t1d6FtOwzlAnQWdyPQKYCPMOLjXcahPJHpfbH4 +KKfnlnGORlF6psRFAuUuFBqDPLm8LK/T6fRJTriVqUfCiqrgpMpXGOaRYftkY8KJ +C9mu4dgfGSycB64yQq0MBg5xABEoFIfeYaIDg2X07X3Hp5UVB1n2tqcgE0ilVDNl +tfacjghnWBO4cI9qNecqWgNjijXO2BH0ZMcpCXxbvHSPYJU8hOnxAwST9A9gGnvJ +s1Xh/Wn8suX1C6+iZa1JEHMyQdwGow== +=vCIm +-----END PGP SIGNATURE-----
