CVE-2025-29891

Published Mar 12, 2025

Last updated 5 months ago

Apache Camel

Overview

AI description

Automated description summarized from trusted sources.

CVE-2025-29891 is a bypass/injection vulnerability that affects Apache Camel versions 4.10.0 before 4.10.2, 4.8.0 before 4.8.5, and 3.10.0 before 3.22.4. It exists in Camel's default incoming header filter, which allows attackers to include Camel-specific headers that can alter the behavior of certain Camel components, such as camel-bean or camel-exec. This vulnerability can be exploited if Camel applications are directly connected to the internet via HTTP. An attacker can include parameters in HTTP requests, either as request parameters or within the request payload, which are then translated into headers. Due to incorrect case-sensitive filtering, attackers can bypass the intended header restrictions by altering the casing of the header names (e.g., using "CAmelExecCommandExecutable" instead of "CamelExecCommandExecutable"). This allows the injection of arbitrary headers, potentially leading to the execution of internal Camel methods.

Description: Bypass/Injection vulnerability in Apache Camel. This issue affects Apache Camel: from 4.10.0 before 4.10.2, from 4.8.0 before 4.8.5, from 3.10.0 before 3.22.4. 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. 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 headers could be both provided as request parameters for an HTTP methods invocation or as part of the payload of the HTTP methods invocation. All the known Camel HTTP component such as camel-servlet, camel-jetty, camel-undertow, camel-platform-http, and camel-netty-http would be vulnerable out of the box. 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.
Source: security@apache.org
NVD status: Analyzed
Products: camel

Risk scores

CVSS 3.1

Type: Secondary
Base score: 4.8
Impact score: 2.5
Exploitability score: 2.2
Vector string: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
Severity: MEDIUM

Weaknesses

security@apache.org: CWE-164

Hype score: Not currently trending

Configurations

[
  {
    "nodes": [
      {
        "negate": false,
        "cpeMatch": [
          {
            "criteria": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
            "vulnerable": true,
            "matchCriteriaId": "F955C7FA-20EE-44FC-BB7F-2734A731A9DC",
            "versionEndExcluding": "3.22.4",
            "versionStartIncluding": "3.10.0"
          },
          {
            "criteria": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
            "vulnerable": true,
            "matchCriteriaId": "15914F75-761B-40AD-8489-EA92699F3741",
            "versionEndExcluding": "4.8.5",
            "versionStartIncluding": "4.8.0"
          },
          {
            "criteria": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
            "vulnerable": true,
            "matchCriteriaId": "DB496A7D-7E5D-48DA-B49F-4494B7369026",
            "versionEndExcluding": "4.10.2",
            "versionStartIncluding": "4.10.0"
          }
        ],
        "operator": "OR"
      }
    ]
  }
]

References

Sources include official advisories and independent security research.