← Übersicht Nicht im beobachteten Stack

Apache Camel AWS2 SNS: An inbound Camel-namespace filter was added to Sns2HeaderFilterStrategy to align it with sibling components

CVE-2026-56140 · GHSA-w2v8-8q6c-3rhr

Kritisch · CVSS 9.8 Red Hat: Low Netzwerk · ohne Login Kein Fix bekannt

Veröffentlicht
06.07.2026 10:16
Zuletzt geändert
26.08.2026
EPSS (30 Tage)
0.7 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Beschreibung

Originaltext der Quelle, nicht übersetzt.

Improper Input Validation vulnerability in Apache Camel AWS SNS component. The camel-aws2-sns component filters Camel headers through a component-specific HeaderFilterStrategy, Sns2HeaderFilterStrategy. Like the sibling Sqs2HeaderFilterStrategy, it originally configured only an outbound filter (setOutFilterPattern, which blocks Camel*, breadcrumbId and org.apache.camel.* headers from being written out) and did not configure an inbound filter rule. For the related camel-aws2-sqs component this inbound gap was exploitable, because the Sqs2Consumer maps inbound SQS message attributes into the Camel Exchange via HeaderFilterStrategy.applyFilterToExternalHeaders, allowing a message sender to inject Camel control headers (tracked as CVE-2026-46456). camel-aws2-sns, by contrast, is producer-only: Sns2Endpoint does not support consumers (createConsumer throws UnsupportedOperationException, 'You cannot receive messages from this endpoint'), so no externally-supplied message attributes are ever mapped inbound into a Camel Exchange through SNS, and the missing inbound filter rule on Sns2HeaderFilterStrategy was therefore not reachable by an attacker. As part of the same fix (CAMEL-23506), an inbound filter rule (setInFilterStartsWith for the Camel namespace) was added to Sns2HeaderFilterStrategy so that its configuration matches the corrected Sqs2HeaderFilterStrategy and the other sibling strategies. This is a defense-in-depth alignment with no known exploit path in camel-aws2-sns. 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. This is a defense-in-depth hardening change with no known exploit path in camel-aws2-sns, which is producer-only, so no urgent action or workaround is required. Users who want the aligned behaviour can upgrade to version 4.21.0, or to 4.14.8 on the 4.14.x LTS releases stream, or to 4.18.3 on the 4.18.x releases stream, which contain the change. As a general best practice, operators should continue to apply least-privilege IAM permissions on their SNS topics.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 4 nicht betroffen.

Nicht betroffen (4)
OpenShift ServerlessNicht betroffenverwundbarer Code nicht enthaltenopenshift-serverless-1/kn-eventing-integrations-aws-sns-sink-rhel9
Red Hat JBoss Enterprise Application Platform Expansion PackNicht betroffenverwundbarer Code nicht enthaltencamel-aws2-sns
Red Hat build of Apache Camel 4 for Quarkus 3Nicht betroffenverwundbarer Code nicht enthaltencamel-aws2-sns
Red Hat build of Apache Camel for Spring Boot 4Nicht betroffenverwundbarer Code nicht enthaltencamel-aws2-sns
Weitere betroffene Pakete (5)
CVEApache Software Foundation/Apache Camel AWS2 SNS4.0.0 → 4.14.8, 4.15.0 → 4.18.3, 4.19.0 → 4.21.0CVE-2026-56140
Mavenorg.apache.camel:camel-aws2-sns4.0.0 → 4.14.8GHSA-w2v8-8q6c-3rhr
Mavenorg.apache.camel:camel-aws2-sns4.15.0 → 4.18.3GHSA-w2v8-8q6c-3rhr
Mavenorg.apache.camel:camel-aws2-sns4.19.0 → 4.21.0GHSA-w2v8-8q6c-3rhr
NVDapache:camel4.0.0 → 4.14.8, 4.15.0 → 4.18.3, 4.19.0 → 4.21.0CVE-2026-56140

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.