First published: Wed Nov 15 2017(Updated: )
Apache Camel's camel-hessian component is vulnerable to Java object de-serialisation vulnerability. De-serializing untrusted data can lead to security flaws. Versions Affected: Camel 2.19.0 to 2.19.3 and Camel 2.20.0 The unsupported Camel 2.x (2.18 and earlier) versions may be also affected. References: <a href="https://camel.apache.org/security-advisories.data/CVE-2017-12633.txt.asc">https://camel.apache.org/security-advisories.data/CVE-2017-12633.txt.asc</a> <a href="https://issues.apache.org/jira/browse/CAMEL-11923">https://issues.apache.org/jira/browse/CAMEL-11923</a>
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Camel | >=2.0.0<2.19.4 | |
Apache Camel | >=2.20.0<2.20.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2017-12633 is critical with a severity value of 9.8 on a scale of 1 to 10.
CVE-2017-12633 affects Apache Camel by allowing an attacker to deserialize a malicious object, potentially leading to Remote Code Execution (RCE).
Versions up to (exclusive) 2.19.4 and versions up to (exclusive) 2.20.1 of Apache Camel are affected by CVE-2017-12633.
CVE-2017-12633 can be remediated by updating to version 2.19.4 or later, or version 2.20.1 or later, of the camel-hessian component.
More information about CVE-2017-12633 can be found at the following references: [1] [2] [3].