Apache Camel's camel-aws2-sqs component contains an improper input validation flaw in its inbound header handling. The component maps inbound Amazon SQS message attributes into the Camel Exchange through a component-specific HeaderFilterStrategy. Sqs2HeaderFilterStrategy was configured only with an outbound filter pattern blocking Camel*, breadcrumbId, and org.apache.camel.* headers from being written to the broker, but it lacked a corresponding inbound filter. Consequently, when Sqs2Consumer copied SQS MessageAttributes into the Exchange via HeaderFilterStrategy.applyFilterToExternalHeaders, DefaultHeaderFilterStrategy applied no inbound restriction and accepted attacker-controlled header names, including Camel-internal control headers such as CamelHttpUri, CamelFileName, and CamelSqlQuery. A sender able to place messages onto a consumed SQS queue could therefore inject arbitrary Camel control headers into the route, where they persist across internal direct, seda, and vm hops and may alter the behavior of downstream producers.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.