CVE-2025-27636

Published Mar 9, 2025

Last updated a year ago

Apache Camel

Overview

AI description

Automated description summarized from trusted sources.

CVE-2025-27636 is a bypass/injection vulnerability found in the Apache Camel Bean component. This vulnerability affects Apache Camel versions 4.10.0 through 4.10.1, 4.8.0 through 4.8.4, and 3.10.0 through 3.22.3. The issue arises when specific HTTP servers (camel-servlet, camel-jetty, camel-undertow, camel-platform-http, or camel-netty-http) are used in conjunction with the camel-bean producer, and the targeted bean has multiple methods. Due to a flaw in the header filtering mechanism, an attacker can manipulate header names to invoke unintended methods on the bean. Exploitation of this vulnerability is possible when a bean has multiple methods and is invoked using the camel-bean component together with specific HTTP servers. The vulnerability stems from a bug in the default filtering mechanism, which only blocks headers starting with "Camel," "camel," or "org.apache.camel." By modifying the casing of these prefixes, an attacker can bypass the filter and inject arbitrary headers, leading to the execution of unintended methods within the bean. Users are advised to upgrade to Apache Camel versions 4.10.2, 4.8.5, or 3.22.4, depending on their current version branch. As a mitigation, headers can be removed within Camel routes using methods like the removeHeaders EIP to filter out headers not adhering to the standard prefixes.

Description: Bypass/Injection vulnerability in Apache Camel components under particular conditions. This issue affects Apache Camel: from 4.10.0 through <= 4.10.1, from 4.8.0 through <= 4.8.4, from 3.10.0 through <= 3.22.3. 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, to call another method on the bean, than was coded in the application. In the camel-jms component, then a malicious header can be used to send the message to another queue (on the same broker) than was coded in the application. This could also be seen by using the camel-exec component The attacker would need to inject custom headers, such as HTTP protocols. So if you have Camel applications that are directly connected to the internet via HTTP, then an attacker could include malicious HTTP headers in the HTTP requests that are send to the Camel application. 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. In these conditions an attacker could be able to forge a Camel header name and make the bean component invoking other methods in the same bean. In terms of usage of the default header filter strategy the list of components using that is: * camel-activemq * camel-activemq6 * camel-amqp * camel-aws2-sqs * camel-azure-servicebus * camel-cxf-rest * camel-cxf-soap * camel-http * camel-jetty * camel-jms * camel-kafka * camel-knative * camel-mail * camel-nats * camel-netty-http * camel-platform-http * camel-rest * camel-sjms * camel-spring-rabbitmq * camel-stomp * camel-tahu * camel-undertow * camel-xmpp The vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with "Camel", "camel", or "org.apache.camel.". Mitigation: You can easily work around this in your Camel applications by removing the headers in your Camel routes. There are many ways of doing this, also globally or per route. This means you could use the removeHeaders EIP, to filter out anything like "cAmel, cAMEL" etc, or in general everything not starting with "Camel", "camel" or "org.apache.camel.".
Source: security@apache.org
NVD status: Analyzed
Products: camel

Risk scores

CVSS 3.1

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

Weaknesses

134c704f-9b21-4f2e-91b3-4a467353bcc0: CWE-178

Hype score: Not currently trending

Configurations

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

References

Sources include official advisories and independent security research.