Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2013-4330

Improper Control of Generation of Code ('Code Injection')

Published: Oct 04, 2013 | Modified: Apr 11, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
6.8 IMPORTANT
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V3
Ubuntu
Vulnerability-free packages from our partners
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2013-4330
CWEhttps://cwe.mitre.org/data/definitions/94.html

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.

Weakness

The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

Affected Software

Name Vendor Start Version End Version
Camel Apache * 2.9.6 (including)
Camel Apache 1.0.0 (including) 1.0.0 (including)
Camel Apache 1.1.0 (including) 1.1.0 (including)
Camel Apache 1.2.0 (including) 1.2.0 (including)
Camel Apache 1.3.0 (including) 1.3.0 (including)
Camel Apache 1.4.0 (including) 1.4.0 (including)
Camel Apache 1.5.0 (including) 1.5.0 (including)
Camel Apache 1.6.0 (including) 1.6.0 (including)
Camel Apache 1.6.1 (including) 1.6.1 (including)
Camel Apache 1.6.2 (including) 1.6.2 (including)
Camel Apache 1.6.3 (including) 1.6.3 (including)
Camel Apache 1.6.4 (including) 1.6.4 (including)
Camel Apache 2.0.0 (including) 2.0.0 (including)
Camel Apache 2.0.0-milestone1 (including) 2.0.0-milestone1 (including)
Camel Apache 2.0.0-milestone2 (including) 2.0.0-milestone2 (including)
Camel Apache 2.0.0-milestone3 (including) 2.0.0-milestone3 (including)
Camel Apache 2.1.0 (including) 2.1.0 (including)
Camel Apache 2.2.0 (including) 2.2.0 (including)
Camel Apache 2.3.0 (including) 2.3.0 (including)
Camel Apache 2.4.0 (including) 2.4.0 (including)
Camel Apache 2.5.0 (including) 2.5.0 (including)
Camel Apache 2.6.0 (including) 2.6.0 (including)
Camel Apache 2.7.0 (including) 2.7.0 (including)
Camel Apache 2.7.1 (including) 2.7.1 (including)
Camel Apache 2.7.2 (including) 2.7.2 (including)
Camel Apache 2.7.3 (including) 2.7.3 (including)
Camel Apache 2.7.4 (including) 2.7.4 (including)
Camel Apache 2.7.5 (including) 2.7.5 (including)
Camel Apache 2.8.0 (including) 2.8.0 (including)
Camel Apache 2.8.1 (including) 2.8.1 (including)
Camel Apache 2.8.2 (including) 2.8.2 (including)
Camel Apache 2.8.3 (including) 2.8.3 (including)
Camel Apache 2.8.4 (including) 2.8.4 (including)
Camel Apache 2.8.5 (including) 2.8.5 (including)
Camel Apache 2.8.6 (including) 2.8.6 (including)
Camel Apache 2.9.0 (including) 2.9.0 (including)
Camel Apache 2.9.1 (including) 2.9.1 (including)
Camel Apache 2.9.2 (including) 2.9.2 (including)
Camel Apache 2.9.3 (including) 2.9.3 (including)
Camel Apache 2.9.4 (including) 2.9.4 (including)
Camel Apache 2.9.5 (including) 2.9.5 (including)
Camel Apache 2.10.0 (including) 2.10.0 (including)
Camel Apache 2.10.1 (including) 2.10.1 (including)
Camel Apache 2.10.2 (including) 2.10.2 (including)
Camel Apache 2.10.3 (including) 2.10.3 (including)
Camel Apache 2.10.4 (including) 2.10.4 (including)
Camel Apache 2.10.5 (including) 2.10.5 (including)
Camel Apache 2.10.6 (including) 2.10.6 (including)
Camel Apache 2.11.0 (including) 2.11.0 (including)
Camel Apache 2.11.1 (including) 2.11.1 (including)
Camel Apache 2.12.0 (including) 2.12.0 (including)
Fuse ESB Enterprise 7.1.0 RedHat *
Fuse Management Console 7.1.0 RedHat *
Fuse MQ Enterprise 7.1.0 RedHat *
Red Hat JBoss A-MQ 6.0 RedHat *
Red Hat JBoss BPMS 6.0 RedHat Camel *
Red Hat JBoss BRMS 6.0 RedHat Camel *
Red Hat JBoss Fuse 6.0 RedHat *
Red Hat JBoss Fuse Service Works 6.0 RedHat Camel *
Red Hat OpenShift Enterprise 2.0 RedHat activemq-0:5.9.0-4.redhat.610328.el6op *
RHEL 6 Version of OpenShift Enterprise 1.2 RedHat activemq-0:5.9.0-4.redhat.610328.el6op *

Potential Mitigations

  • Run your code in a “jail” or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product.
  • Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection.
  • This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise.
  • Be careful to avoid CWE-243 and other weaknesses related to jails.
  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of code injection, use stringent allowlists that limit which constructs are allowed. If you are dynamically constructing code that invokes a function, then verifying that the input is alphanumeric might be insufficient. An attacker might still be able to reference a dangerous function that you did not intend to allow, such as system(), exec(), or exit().
  • For Python programs, it is frequently encouraged to use the ast.literal_eval() function instead of eval, since it is intentionally designed to avoid executing code. However, an adversary could still cause excessive memory or stack consumption via deeply nested structures [REF-1372], so the python documentation discourages use of ast.literal_eval() on untrusted data [REF-1373].

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2025 Aqua Security Software Ltd.   Privacy Policy | Terms of Use