Unscored severity · published Oct 4, 2013
CVE-2013-4330
Apache Camel before 2.9.7, 2.10.0 before 2.10.7, 2.11.0 before 2.11.2, and 2.12.0 allows remote attackers to execute arbitrary simple language expressions by including "$simple{}"…
–
CVSS
8.5%
EPSS
No
On KEV
Description
Apache Camel before 2.9.7, 2.10.0 before 2.10.7, 2.11.0 before 2.11.2, and 2.12.0 allows remote attackers to execute arbitrary simple language expressions by including "$simple{}" in a CamelFileName message header to a (1) FILE or (2) FTP producer.
Exploitation
Is it being used?
Exploit prediction (EPSS)8.5% · higher than 95% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
CA
Camel · Apache
through 2.9.6; 1.0.0; 1.1.0; 1.2.0; 1.3.0; 1.4.0; +34 more · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2013-4330
CVE.org
https://www.cve.org/CVERecord?id=CVE-2013-4330
Vendor Advisory
http://camel.apache.org/security-advisories.data/CVE-2013-4330.txt.asc?version=1&modificationDate=1380535446943
osvdb.org
http://osvdb.org/97941
packetstormsecurity.com
http://packetstormsecurity.com/files/123454/
rhn.redhat.com
http://rhn.redhat.com/errata/RHSA-2013-1862.html
rhn.redhat.com
http://rhn.redhat.com/errata/RHSA-2014-0124.html
rhn.redhat.com
http://rhn.redhat.com/errata/RHSA-2014-0140.html
More from Camel
10.0
CVE-2026-33453
Apache Camel: CoAP URI Query Parameter to Exchange Header Injection in camel-coap Allows Single-Packet Pre-Auth Remote Code Execution
9.9
CVE-2026-40453
Apache Camel JMS, Apache Camel CoAP, Apache Camel Google PubSub: Incomplete fix for CVE-2025-27636 in non-HTTP HeaderFilterStrategies (camel-jms, camel-sjms, camel-coap, camel-google-pubsub) allows case-variant header injection
9.8
CVE-2026-80351
Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod
9.8
CVE-2026-80352
Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects
9.8
CVE-2026-78329
Apache Camel: Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes