First published: Thu Feb 09 2017(Updated: )
Apache Camel's camel-jackson and camel-jacksonxml components are vulnerable to Java object de-serialisation vulnerability. Camel allows to specify such a type through the 'CamelJacksonUnmarshalType' property. De-serializing untrusted data can lead to security flaws as demonstrated in various similar reports about Java de-serialization issues. Mitigation: 2.16.x users should upgrade to 2.16.5, 2.17.x users should upgrade to 2.17.5, 2.18.x users should upgrade to 2.18.2. The JIRA tickets: https://issues.apache.org/jira/browse/CAMEL-10567 and https://issues.apache.org/jira/browse/CAMEL-10604 refers to the various commits that resovoled the issue, and have more details.
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.apache.camel:camel-jackson | >=2.18.0<2.18.2 | 2.18.2 |
maven/org.apache.camel:camel-jackson | >=2.17.0<2.17.5 | 2.17.5 |
maven/org.apache.camel:camel-jackson | <2.16.5 | 2.16.5 |
Apache Camel | =2.16.0 | |
Apache Camel | =2.16.1 | |
Apache Camel | =2.16.2 | |
Apache Camel | =2.16.3 | |
Apache Camel | =2.16.4 | |
Apache Camel | =2.17.0 | |
Apache Camel | =2.17.1 | |
Apache Camel | =2.17.2 | |
Apache Camel | =2.17.3 | |
Apache Camel | =2.17.4 | |
Apache Camel | =2.18.0 | |
Apache Camel | =2.18.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.