Vulnerability-Lookup

CNVD-2025-05169

Vulnerability from cnvd - Published: 2025-03-17

Title

Apache Camel任意命令执⾏漏洞

Description

Apache Camel是美国阿帕奇（Apache）基金会的一套开源的基于Enterprise Integration Pattern（企业整合模式，简称EIP）的集成框架。该框架提供企业集成模式的Java对象（POJO）的实现，且通过应用程序接口来配置路由和中介的规则。 Apache Camel存在任意命令执⾏漏洞，该漏洞是由于Apache Camel对请求头⼤⼩写处理不当，攻击者可利用该漏洞通过传递特殊格式的头部（如"CAmelExecCommandExecutable"而非"CamelExecCommandExecutable"）绕过安全过滤，覆盖预定义命令，导致任意命令执⾏。

Severity

高

Patch Name

Apache Camel任意命令执⾏漏洞的补丁

Patch Description

Formal description

厂商已提供漏洞修补方案，请关注厂商主页及时更新： http://www.apache.org/

Reference

https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC

Impacted products

Name
['Apache Camel >=4.10.0，<=4.10.1', 'Apache Camel >=4.8.0，<=4.8.4', 'Apache Camel >=3.10.0，<=3.22.3']

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2025-27636"
    }
  },
  "description": "Apache Camel\u662f\u7f8e\u56fd\u963f\u5e15\u5947\uff08Apache\uff09\u57fa\u91d1\u4f1a\u7684\u4e00\u5957\u5f00\u6e90\u7684\u57fa\u4e8eEnterprise Integration Pattern\uff08\u4f01\u4e1a\u6574\u5408\u6a21\u5f0f\uff0c\u7b80\u79f0EIP\uff09\u7684\u96c6\u6210\u6846\u67b6\u3002\u8be5\u6846\u67b6\u63d0\u4f9b\u4f01\u4e1a\u96c6\u6210\u6a21\u5f0f\u7684Java\u5bf9\u8c61\uff08POJO\uff09\u7684\u5b9e\u73b0\uff0c\u4e14\u901a\u8fc7\u5e94\u7528\u7a0b\u5e8f\u63a5\u53e3\u6765\u914d\u7f6e\u8def\u7531\u548c\u4e2d\u4ecb\u7684\u89c4\u5219\u3002\n\nApache Camel\u5b58\u5728\u4efb\u610f\u547d\u4ee4\u6267\u2f8f\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u662f\u7531\u4e8eApache Camel\u5bf9\u8bf7\u6c42\u5934\u2f24\u2f29\u5199\u5904\u7406\u4e0d\u5f53\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u901a\u8fc7\u4f20\u9012\u7279\u6b8a\u683c\u5f0f\u7684\u5934\u90e8\uff08\u5982\"CAmelExecCommandExecutable\"\u800c\u975e\"CamelExecCommandExecutable\"\uff09\u7ed5\u8fc7\u5b89\u5168\u8fc7\u6ee4\uff0c\u8986\u76d6\u9884\u5b9a\u4e49\u547d\u4ee4\uff0c\u5bfc\u81f4\u4efb\u610f\u547d\u4ee4\u6267\u2f8f\u3002",
  "formalWay": "\u5382\u5546\u5df2\u63d0\u4f9b\u6f0f\u6d1e\u4fee\u8865\u65b9\u6848\uff0c\u8bf7\u5173\u6ce8\u5382\u5546\u4e3b\u9875\u53ca\u65f6\u66f4\u65b0\uff1a\r\nhttp://www.apache.org/",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2025-05169",
  "openTime": "2025-03-17",
  "patchDescription": "Apache Camel\u662f\u7f8e\u56fd\u963f\u5e15\u5947\uff08Apache\uff09\u57fa\u91d1\u4f1a\u7684\u4e00\u5957\u5f00\u6e90\u7684\u57fa\u4e8eEnterprise Integration Pattern\uff08\u4f01\u4e1a\u6574\u5408\u6a21\u5f0f\uff0c\u7b80\u79f0EIP\uff09\u7684\u96c6\u6210\u6846\u67b6\u3002\u8be5\u6846\u67b6\u63d0\u4f9b\u4f01\u4e1a\u96c6\u6210\u6a21\u5f0f\u7684Java\u5bf9\u8c61\uff08POJO\uff09\u7684\u5b9e\u73b0\uff0c\u4e14\u901a\u8fc7\u5e94\u7528\u7a0b\u5e8f\u63a5\u53e3\u6765\u914d\u7f6e\u8def\u7531\u548c\u4e2d\u4ecb\u7684\u89c4\u5219\u3002\r\n\r\nApache Camel\u5b58\u5728\u4efb\u610f\u547d\u4ee4\u6267\u2f8f\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u662f\u7531\u4e8eApache Camel\u5bf9\u8bf7\u6c42\u5934\u2f24\u2f29\u5199\u5904\u7406\u4e0d\u5f53\uff0c\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u901a\u8fc7\u4f20\u9012\u7279\u6b8a\u683c\u5f0f\u7684\u5934\u90e8\uff08\u5982\"CAmelExecCommandExecutable\"\u800c\u975e\"CamelExecCommandExecutable\"\uff09\u7ed5\u8fc7\u5b89\u5168\u8fc7\u6ee4\uff0c\u8986\u76d6\u9884\u5b9a\u4e49\u547d\u4ee4\uff0c\u5bfc\u81f4\u4efb\u610f\u547d\u4ee4\u6267\u2f8f\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "Apache Camel\u4efb\u610f\u547d\u4ee4\u6267\u2f8f\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "Apache Camel \u003e=4.10.0\uff0c\u003c=4.10.1",
      "Apache Camel \u003e=4.8.0\uff0c\u003c=4.8.4",
      "Apache Camel \u003e=3.10.0\uff0c\u003c=3.22.3"
    ]
  },
  "referenceLink": "https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC",
  "serverity": "\u9ad8",
  "submitTime": "2025-03-13",
  "title": "Apache Camel\u4efb\u610f\u547d\u4ee4\u6267\u2f8f\u6f0f\u6d1e"
}

CVE-2025-27636 (GCVE-0-2025-27636)

Vulnerability from cvelistv5 – Published: 2025-03-09 12:09 – Updated: 2026-02-26 19:09

Title

Apache Camel: Camel Message Header Injection via Improper Filtering

Summary

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.".

Severity

5.6 (Medium)


                        
                          CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

SSVC

Exploitation: poc Automatable: no Technical Impact: partial

CISA Coordinator · CISA-ADP (v2.0.3)

Decision recorded 2025-10-22 03:55 UTC

CWE

Bypass/Injection
CWE-178 - Improper Handling of Case Sensitivity

Assigner

apache mitre root

References

6 references

URL	Tags
https://lists.apache.org/thread/l3zcg3vts88bmc7w8…	vendor-advisory
https://issues.apache.org/jira/browse/CAMEL-21828	issue-tracking
https://camel.apache.org/security/CVE-2025-27636.html	vendor-advisory
http://www.openwall.com/lists/oss-security/2025/03/09/1
https://github.com/akamai/CVE-2025-27636-Apache-C…	exploit
https://camel.apache.org/security/CVE-2025-27636.…	vendor-advisory

Impacted products

1 product

Vendor	Product	Version
Apache Software Foundation	Apache Camel	Affected: 4.10.0 , < 4.10.2 (semver) Affected: 4.8.0 , < 4.8.5 (semver) Affected: 3.10.0 , < 3.22.4 (semver)

Credits

Mark Thorson

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2025-03-09T17:02:21.478Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "http://www.openwall.com/lists/oss-security/2025/03/09/1"
          }
        ],
        "title": "CVE Program Container"
      },
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "HIGH",
              "attackVector": "NETWORK",
              "availabilityImpact": "LOW",
              "baseScore": 5.6,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "LOW",
              "integrityImpact": "LOW",
              "privilegesRequired": "NONE",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2025-27636",
                "options": [
                  {
                    "Exploitation": "poc"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-10-22T03:55:18.536426Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-178",
                "description": "CWE-178 Improper Handling of Case Sensitivity",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-02-26T19:09:44.229Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "references": [
          {
            "tags": [
              "exploit"
            ],
            "url": "https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC/blob/main/src/main/java/com/example/camel/VulnerableCamel.java"
          },
          {
            "tags": [
              "vendor-advisory"
            ],
            "url": "https://camel.apache.org/security/CVE-2025-27636.txt.asc"
          }
        ],
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "collectionURL": "https://repo.maven.apache.org/maven2",
          "defaultStatus": "unaffected",
          "packageName": "org.apache.camel:camel",
          "product": "Apache Camel",
          "vendor": "Apache Software Foundation",
          "versions": [
            {
              "lessThan": "4.10.2",
              "status": "affected",
              "version": "4.10.0",
              "versionType": "semver"
            },
            {
              "lessThan": "4.8.5",
              "status": "affected",
              "version": "4.8.0",
              "versionType": "semver"
            },
            {
              "lessThan": "3.22.4",
              "status": "affected",
              "version": "3.10.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Mark Thorson"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eBypass/Injection vulnerability in Apache Camel components under particular conditions.\u003c/p\u003e\u003cp\u003eThis issue affects Apache Camel: from 4.10.0 through \u0026lt;= 4.10.1, from 4.8.0 through \u0026lt;= 4.8.4, from 3.10.0 through \u0026lt;= 3.22.3.\u003c/p\u003e\u003cp\u003eUsers 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.\u003c/p\u003e\u003cdiv\u003e\u003c/div\u003e\u003cdiv\u003eThis vulnerability is present in Camel\u0027s default incoming header filter, that allows an attacker to include Camel specific\u003c/div\u003e\u003cdiv\u003eheaders that for some Camel components can alter the behaviours such as the camel-bean component, to call another method\u003c/div\u003e\u003cdiv\u003eon the bean, than was coded in the application. In the camel-jms component, then a malicious header can be used to send\u003c/div\u003e\u003cdiv\u003ethe 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\u003c/div\u003e\u003cdiv\u003e\u003cbr\u003e\u003c/div\u003e\u003cdiv\u003eThe attacker would need to inject custom headers, such as HTTP protocols. So if you have Camel applications that are\u003c/div\u003e\u003cdiv\u003edirectly connected to the internet via HTTP, then an attacker could include malicious HTTP headers in the HTTP requests\u003c/div\u003e\u003cdiv\u003ethat are send to the Camel application.\u003c/div\u003e\u003cdiv\u003e\u003cbr\u003e\u003c/div\u003eAll 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.\u003cbr\u003e\u003cbr\u003eIn 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.\u003cbr\u003e\u003cbr\u003e\u003cdiv\u003eIn terms of usage of the default header filter strategy the list of components using that is: \u003cbr\u003e\u003c/div\u003e\u003cdiv\u003e\u003cdiv\u003e\u003cul\u003e\u003cli\u003ecamel-activemq\u003c/li\u003e\u003cli\u003ecamel-activemq6\u003c/li\u003e\u003cli\u003ecamel-amqp\u003c/li\u003e\u003cli\u003ecamel-aws2-sqs\u003c/li\u003e\u003cli\u003ecamel-azure-servicebus\u003c/li\u003e\u003cli\u003ecamel-cxf-rest\u003c/li\u003e\u003cli\u003ecamel-cxf-soap\u003c/li\u003e\u003cli\u003ecamel-http\u003c/li\u003e\u003cli\u003ecamel-jetty\u003c/li\u003e\u003cli\u003ecamel-jms\u003c/li\u003e\u003cli\u003ecamel-kafka\u003c/li\u003e\u003cli\u003ecamel-knative\u003c/li\u003e\u003cli\u003ecamel-mail\u003c/li\u003e\u003cli\u003ecamel-nats\u003c/li\u003e\u003cli\u003ecamel-netty-http\u003c/li\u003e\u003cli\u003ecamel-platform-http\u003c/li\u003e\u003cli\u003ecamel-rest\u003c/li\u003e\u003cli\u003ecamel-sjms\u003c/li\u003e\u003cli\u003ecamel-spring-rabbitmq\u003c/li\u003e\u003cli\u003ecamel-stomp\u003c/li\u003e\u003cli\u003ecamel-tahu\u003c/li\u003e\u003cli\u003ecamel-undertow\u003c/li\u003e\u003cli\u003ecamel-xmpp\u003c/li\u003e\u003c/ul\u003e\u003c/div\u003e\u003c/div\u003e\u003cdiv\u003eThe vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with \"Camel\", \"camel\", or \"org.apache.camel.\".\u0026nbsp;\u003c/div\u003e\u003cbr\u003e\u003cdiv\u003e\u003cspan style=\"background-color: var(--wht);\"\u003eMitigation:\u0026nbsp;\u003c/span\u003eYou can easily work around this in your Camel applications by removing the\u0026nbsp;headers in your Camel routes. There are many ways of doing this, also\u0026nbsp;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.\".\u0026nbsp;\u003cbr\u003e\u003c/div\u003e\u003cbr\u003e"
            }
          ],
          "value": "Bypass/Injection vulnerability in Apache Camel components under particular conditions.\n\nThis issue affects Apache Camel: from 4.10.0 through \u003c= 4.10.1, from 4.8.0 through \u003c= 4.8.4, from 3.10.0 through \u003c= 3.22.3.\n\nUsers 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.\n\n\n\nThis vulnerability is present in Camel\u0027s default incoming header filter, that allows an attacker to include Camel specific\n\nheaders that for some Camel components can alter the behaviours such as the camel-bean component, to call another method\n\non the bean, than was coded in the application. In the camel-jms component, then a malicious header can be used to send\n\nthe 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\n\n\n\n\nThe attacker would need to inject custom headers, such as HTTP protocols. So if you have Camel applications that are\n\ndirectly connected to the internet via HTTP, then an attacker could include malicious HTTP headers in the HTTP requests\n\nthat are send to the Camel application.\n\n\n\n\nAll 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.\n\nIn 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.\n\nIn terms of usage of the default header filter strategy the list of components using that is: \n\n\n  *  camel-activemq\n  *  camel-activemq6\n  *  camel-amqp\n  *  camel-aws2-sqs\n  *  camel-azure-servicebus\n  *  camel-cxf-rest\n  *  camel-cxf-soap\n  *  camel-http\n  *  camel-jetty\n  *  camel-jms\n  *  camel-kafka\n  *  camel-knative\n  *  camel-mail\n  *  camel-nats\n  *  camel-netty-http\n  *  camel-platform-http\n  *  camel-rest\n  *  camel-sjms\n  *  camel-spring-rabbitmq\n  *  camel-stomp\n  *  camel-tahu\n  *  camel-undertow\n  *  camel-xmpp\n\n\n\n\n\n\nThe vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with \"Camel\", \"camel\", or \"org.apache.camel.\".\u00a0\n\n\nMitigation:\u00a0You can easily work around this in your Camel applications by removing the\u00a0headers in your Camel routes. There are many ways of doing this, also\u00a0globally 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.\"."
        }
      ],
      "metrics": [
        {
          "other": {
            "content": {
              "text": "moderate"
            },
            "type": "Textual description of severity"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "Bypass/Injection",
              "lang": "en"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-03-17T14:42:57.795Z",
        "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
        "shortName": "apache"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://lists.apache.org/thread/l3zcg3vts88bmc7w8172wkgw610y693z"
        },
        {
          "tags": [
            "issue-tracking"
          ],
          "url": "https://issues.apache.org/jira/browse/CAMEL-21828"
        },
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://camel.apache.org/security/CVE-2025-27636.html"
        }
      ],
      "source": {
        "defect": [
          "CAMEL-21828"
        ],
        "discovery": "UNKNOWN"
      },
      "title": "Apache Camel: Camel Message Header Injection via Improper Filtering",
      "x_generator": {
        "engine": "Vulnogram 0.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
    "assignerShortName": "apache",
    "cveId": "CVE-2025-27636",
    "datePublished": "2025-03-09T12:09:58.619Z",
    "dateReserved": "2025-03-04T11:56:29.254Z",
    "dateUpdated": "2026-02-26T19:09:44.229Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

CNVD-2025-05169

CVE-2025-27636 (GCVE-0-2025-27636)

Tags

Sightings

Nomenclature

Related by attack behaviour