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 03a34e71 Update CVE
03a34e71 is described below
commit 03a34e71e11bd2c713e04c70ddd48330b4a70be3
Author: Andrea Cosentino <[email protected]>
AuthorDate: Wed Mar 12 16:48:09 2025 +0100
Update CVE
Signed-off-by: Andrea Cosentino <[email protected]>
---
content/security/CVE-2025-29891.md | 2 +-
content/security/CVE-2025-29891.txt.asc | 18 +++++++++---------
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/content/security/CVE-2025-29891.md
b/content/security/CVE-2025-29891.md
index b3648bd6..2f4832fe 100644
--- a/content/security/CVE-2025-29891.md
+++ b/content/security/CVE-2025-29891.md
@@ -9,7 +9,7 @@ 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 [...]
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 Ryan Barnett of Akamai Security
Intelligence Group (SIG)"
+credit: "This issue was discovered by Citi Cyber Security Operations and
reported by Akamai Security Intelligence Group (SIG)"
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
---
diff --git a/content/security/CVE-2025-29891.txt.asc
b/content/security/CVE-2025-29891.txt.asc
index f76287be..8b90a1c4 100644
--- a/content/security/CVE-2025-29891.txt.asc
+++ b/content/security/CVE-2025-29891.txt.asc
@@ -12,7 +12,7 @@ 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 [...]
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 Ryan Barnett of Akamai Security
Intelligence Group (SIG)"
+credit: "This issue was discovered by Citi Cyber Security Operations and
reported by Akamai Security Intelligence Group (SIG)"
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/QQAFAmfRl+MACgkQ406fOAL/
-QQBa0wf/ZnUKPl5hlkSAXMiDdVPJx1v/ElaWrnKufCd+2aiefK44IiNjX3keRAkt
-nHPdNBIv/+qiEqKPv8CMuMYiC8s8S66yXenSXp3fEnrABMganZM+ibGmHnN2jTs3
-2EpYxQ6xGsx3AJBT5DmscnrypC2eMBNn0xsNW2kJp878nnwyalZBJhbdtYOHBWdP
-0znvaPzfGxHzguCRP/ohG3o7SpunUitsuhsDpJDeHeoYZK6rl3qDeZWx9JiLgkGp
-vl2zDGNHoA1ctSZUGMk+HXHdLXTHXjqjRf6ahdP5z9wcF9Q64RP7XBMkQZMllRgL
-k41mrx9TINgMjOocnmceh43bjEst5g==
-=P7KQ
+iQEzBAEBCAAdFiEEJ2Y0ButtuvUpHyYV406fOAL/QQAFAmfRrJ8ACgkQ406fOAL/
+QQCcAggAsR7IxwcNJFdy0LQw6pJmcU7V62y5QQCExZyROmZzCvhb3EJKsOiKid+l
+toAdAEyHFRTBA7G1Yrljn2bayg/0fn+MOCn4XMoZICW3uyTY6PKS+ySUH6IW6pBk
+IdcGB9mq1lFHCI0b2tObfY9QSlFJ2Ft+YfPvinsNJpqYgkiHqiUNWNEeYCR09mSV
+S5h4o9SI/MOiT/tfp10F6kjfd+4XJm3r5EMG+EKb35s8A2GA2l3mJSKDNAzcZUS9
+NkOYmeE9hI/WOVy0I1XJihLpzQ9TzYjKToWb4OVHwMX2WMZ7d7lRQX+5whQLI92d
+rPTAJXRaPSltK5p1i2bgnhTEw+Vl4A==
+=Q72A
-----END PGP SIGNATURE-----
