SecBoard
Zurück zur CVE-Übersicht

CVE-2026-46592

HIGH(7.5)

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

Risk Signal Score19/100 — NIEDRIG
  • CVSS 7.5 — Hoch

Erwähnungen (letzte 60 Tage)

Artikel

EPSS-Score

0.6%

Exploit-Wahrscheinlichkeit (30 Tage)

CVSS Score

7.5

Technische Schwere

Beschreibung

Improper Input Validation, Unintended Proxy or Intermediary ('Confused Deputy') vulnerability in Apache Camel CXF SOAP component. The camel-cxf producer selects which SOAP operation to invoke on the backend service from the operationName (and operationNamespace) Exchange header, whose constant values (CxfConstants.OPERATION_NAME / OPERATION_NAMESPACE) were the plain strings operationName / operationNamespace. Because these names do not start with the Camel / camel prefix, HttpHeaderFilterStrategy - which blocks only the Camel header namespace on the HTTP boundary - let them pass from an inbound HTTP request straight into the Exchange. In a route that bridges an HTTP consumer (for example platform-http) into a cxf: producer, any HTTP client could therefore set the operationName header and have CxfProducer resolve and invoke a different WSDL operation than the route intended - for example replacing a read operation with a destructive one - against the backend SOAP service (a confused-deputy redirection). The constant is defined in the shared camel-cxf-common module, so the same non-prefixed names also applied to camel-cxfrs. No credentials are required when the bridging consumer is unauthenticated. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. After upgrading, the operation-selection headers are named CamelCxfOperationName / CamelCxfOperationNamespace and are filtered at transport boundaries; see the 4.21 upgrade guide for the cross-transport carrier-header pattern. For deployments that cannot upgrade immediately, do not select the CXF operation from untrusted input: strip the operationName and operationNamespace headers from any untrusted ingress before the cxf: producer and set the operation from a trusted source in the route.

Erkennung & Indikatoren

Ausnutzung

In den geprüften Quellen nicht genannt

Behobene Versionen

  • 4.14.8
  • 4.18.3
  • 4.21.0

Threat-Hunting-Queries

Diese Schwachstelle betrifft die Art und Weise, wie Apache Camel CXF SOAP-Operationen aus HTTP-Headern verarbeitet. Eine Verhaltenserkennung sollte auf ungewöhnliche oder nicht autorisierte SOAP-Operationen abzielen, die über HTTP-Anfragen initiiert werden, insbesondere wenn der 'operationName'-Header in der Anfrage manipuliert wurde, um eine andere als die beabsichtigte Operation aufzurufen. Dies

Sentinel/Defender KQL

let suspicious_operation_names = dynamic(['operationName', 'operationNamespace']);
HttpRequests
| where Url contains "/cxf/"
| where CustomHeaders has_any (suspicious_operation_names)
| where CustomHeaders contains "operationName=" or CustomHeaders contains "operationNamespace="
| summarize count() by bin(5m), ClientIP, UserAgent, Url, CustomHeaders
| where count_ > 1 // Adjust threshold as needed for your environment
| project-away count_

Splunk SPL

sourcetype=access_combined (uri_path="/cxf/*" OR uri_path="*soap*") (http_header="*operationName=*" OR http_header="*operationNamespace=*")
| stats count by clientip, useragent, uri_path, http_header
| where count > 1

Sigma

title: Apache Camel CXF Confused Deputy Attempt
id: 00000000-0000-0000-0000-000000000000
status: experimental
description: Detects attempts to exploit CVE-2026-46592 in Apache Camel CXF by manipulating SOAP operation headers.
references:
  - https://camel.apache.org/security/CVE-2026-46592.html
author: SecBoard
date: 2026/07/05
logsource:
  category: webserver
  product: apache
detection:
  selection:
    uri|contains: '/cxf/'
    http_header|contains:
      - 'operationName='
      - 'operationNamespace='
  condition: selection
level: high

Elastic ES|QL

FROM http_logs
| WHERE url.path LIKE '/cxf/%'
| WHERE http.request.headers.operationName IS NOT NULL OR http.request.headers.operationNamespace IS NOT NULL
| GROUP BY client.ip, user_agent.original, url.original, http.request.headers
| AGG count = COUNT()
| WHERE count > 1

SecBoard-generated · behavioral · requires customizationVon SecBoard erzeugt und nicht in einer Zielumgebung validiert. Vor dem Einsatz an die eigene Protokollierung anpassen.

Indikatoren

Datei-Hashes (3)

  • 7240570a05687792c95badfa8d11ed2644117230
  • 36a5088b58be38317a8f974ffda2a262fa00b4e4
  • 0138da45fc9428172c1585ab4561d42e8868cf49

Übernommen wurden nur Indikatoren, die wörtlich in einer Hersteller- oder Research-Quelle standen.

GitHub Advisories

GHSA-mrrp-9gjm-749vHIGH

Apache Camel-CXF: The SOAP operation-selection headers used non-Camel-prefixed names (operationName, operationNamespace) that bypass the HTTP header filter, allowing an HTTP client to redirect the invoked SOAP operation

maven/org.apache.camel:camel-cxf-soap4.14.8
GitHub Advisory

Referenzen