This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-website.git
The following commit(s) were added to refs/heads/main by this push:
new 3d1f9a3d Update CVE
3d1f9a3d is described below
commit 3d1f9a3d39ec6294610c705f13af456e09296cd7
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Thu Mar 13 10:38:00 2025 +0100
Update CVE
Signed-off-by: Andrea Cosentino <anco...@gmail.com>
---
content/security/CVE-2025-29891.txt.asc | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/content/security/CVE-2025-29891.txt.asc
b/content/security/CVE-2025-29891.txt.asc
index 8b90a1c4..9ab3cff1 100644
--- a/content/security/CVE-2025-29891.txt.asc
+++ b/content/security/CVE-2025-29891.txt.asc
@@ -10,9 +10,9 @@ type: security-advisory
cve: CVE-2025-29891
severity: HIGH
summary: "Camel Message Header Injection through request parameters"
-description: "This vulnerability is present in Camel's default incoming header
filter, that allows an attacker to include Camel specific headers that for some
Camel components can alter the behaviours such as the camel-bean component, or
the camel-exec component. If you have Camel applications that are directly
connected to the internet via HTTP, then an attacker could include parameters
in the HTTP requests that are sent to the Camel application that incorrectly
get translated into head [...]
+description: "This vulnerability is present in Camel's default incoming header
filter, that allows an attacker to include Camel specific headers that for some
Camel components can alter the behaviours such as the camel-bean component, or
the camel-exec component. If you have Camel applications that are directly
connected to the internet via HTTP, then an attacker could include parameters
in the HTTP requests that are sent to the Camel application that get translated
into headers. The hea [...]
mitigation: "Users are recommended to upgrade to version 4.10.2 for 4.10.x
LTS, 4.8.5 for 4.8.x LTS and 3.22.4 for 3.x releases. Also, users could use
removeHeaders EIP, to filter out anything like 'cAmel, cAMEL' etc, or in
general everything not starting with 'Camel', 'camel' or 'org.apache.camel.'."
-credit: "This issue was discovered by Citi Cyber Security Operations and
reported by Akamai Security Intelligence Group (SIG)"
+credit: "This issue was discovered by Citi Cyber Security Operations and
reported by Akamai Security Intelligence Group (SIG). This issue was discovered
and reported by Mark Thorson of AT&T."
affected: Apache Camel 4.10.0 before 4.10.2. Apache Camel 4.8.0 before 4.8.5.
Apache Camel 3.10.0 before 3.22.4.
fixed: 3.22.4, 4.8.5 and 4.10.2
- ---
@@ -21,12 +21,12 @@ The JIRA ticket:
https://issues.apache.org/jira/browse/CAMEL-21828 refers to the
This CVE is related to the CVE-2025-27636: while they have the same root cause
and are fixed with the same fix, CVE-2025-27636 was assumed to only be
exploitable if an attacker could add malicious HTTP headers, while we have now
determined that it is also exploitable via HTTP parameters. Like in
CVE-2025-27636, exploitation is only possible if the Camel route uses
particular vulnerable components.
-----BEGIN PGP SIGNATURE-----
-iQEzBAEBCAAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmfRrJ8ACgkQ406fOAL/
-QQCcAggAsR7IxwcNJFdy0LQw6pJmcU7V62y5QQCExZyROmZzCvhb3EJKsOiKid+l
-toAdAEyHFRTBA7G1Yrljn2bayg/0fn+MOCn4XMoZICW3uyTY6PKS+ySUH6IW6pBk
-IdcGB9mq1lFHCI0b2tObfY9QSlFJ2Ft+YfPvinsNJpqYgkiHqiUNWNEeYCR09mSV
-S5h4o9SI/MOiT/tfp10F6kjfd+4XJm3r5EMG+EKb35s8A2GA2l3mJSKDNAzcZUS9
-NkOYmeE9hI/WOVy0I1XJihLpzQ9TzYjKToWb4OVHwMX2WMZ7d7lRQX+5whQLI92d
-rPTAJXRaPSltK5p1i2bgnhTEw+Vl4A==
-=Q72A
+iQEzBAEBCAAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmfSp2kACgkQ406fOAL/
+QQCi2QgAjo5WTqsVV1N9uJUGv5a8oqfCAx/0j3fcFxcID7rj9jB3yarkh/KBf1el
+Y0TQChT8yc5sadKwODsWRXk8jYTzFA1NyDM02E1gJRTFrEDEbydzaS12DIdm2+UR
+cNSE0l0o3mmkC1sInvXAlglZGwNXMrXV/n9k9NE6UFk2qQOYaEU+SW5uYCSJGvdV
+K0mtE3zRlKh704HWxjtuPTPKgRo1hRkQgOFAwT4vmoEZJXAUPBEGMvFlIwv16OKx
+h4Jw6QPyAEihlTogYdjUFlajZtbaqtVB1BzgyinvH9XeJEVR4Zly+7RGubD0OGtq
++9amDZ5wcywt0EBqYsxFN/Tz0CJJGw==
+=71Oy
-----END PGP SIGNATURE-----
