First published: Thu Feb 09 2017(Updated: )
Apache Camel's camel-snakeyaml component is vulnerable to Java object de-serialisation vulnerability. De-serializing untrusted data can lead to security flaws. External References: <a href="http://camel.apache.org/security-advisories.data/CVE-2017-3159.txt.asc">http://camel.apache.org/security-advisories.data/CVE-2017-3159.txt.asc</a> Upstream bug: <a href="https://issues.apache.org/jira/browse/CAMEL-10575">https://issues.apache.org/jira/browse/CAMEL-10575</a>
Credit: security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.apache.camel:camel-snakeyaml | >=2.18.0<2.18.2 | 2.18.2 |
maven/org.apache.camel:camel-snakeyaml | <2.17.5 | 2.17.5 |
redhat/camel-snakeyaml | <2.17.5 | 2.17.5 |
Red Hat Build of Apache Camel | <=2.14.4 | |
Red Hat Build of Apache Camel | >=2.17.0<=2.17.4 | |
Red Hat Build of Apache Camel | >=2.18.0<=2.18.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-3159 has a moderate severity level due to the potential for exploitation through Java object de-serialization.
To remediate CVE-2017-3159, upgrade the camel-snakeyaml component to version 2.18.2 or apply the patch available for version 2.17.5.
The impact of CVE-2017-3159 includes the risk of remote code execution if untrusted data is de-serialized.
Apache Camel versions prior to 2.18.2, including 2.14.4, 2.17.0 to 2.17.4, and 2.18.0 to 2.18.1 are affected by CVE-2017-3159.
No specific workarounds are recommended for CVE-2017-3159; upgrading to the fixed version is the best approach.