CVE-2016-8749
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
| 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 |
| redhat/camel-jackson | <2.17.5 | 2.17.5 |
| redhat/camel-jacksonxml | <2.17.5 | 2.17.5 |
| Red Hat Build of Apache Camel | =2.16.0 | |
| Red Hat Build of Apache Camel | =2.16.1 | |
| Red Hat Build of Apache Camel | =2.16.2 | |
| Red Hat Build of Apache Camel | =2.16.3 | |
| Red Hat Build of Apache Camel | =2.16.4 | |
| Red Hat Build of Apache Camel | =2.17.0 | |
| Red Hat Build of Apache Camel | =2.17.1 | |
| Red Hat Build of Apache Camel | =2.17.2 | |
| Red Hat Build of Apache Camel | =2.17.3 | |
| Red Hat Build of Apache Camel | =2.17.4 | |
| Red Hat Build of Apache Camel | =2.18.0 | |
| Red Hat Build of Apache Camel | =2.18.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://nvd.nist.gov/vuln/detail/CVE-2016-8749
- https://access.redhat.com/errata/RHSA-2017:1832
- https://github.com/advisories/GHSA-vvjc-q5vr-52q6 (Advisory)
- https://lists.apache.org/thread.html/2318d7f7d87724d8716cd650c21b31cb06e4d34f6d0f5ee42f28fdaf@%3Ccommits.camel.apache.org%3E
- https://lists.apache.org/thread.html/b4014ea7c5830ca1fc28edd5cafedfe93ad4af2d9e69c961c5def31d@%3Ccommits.camel.apache.org%3E
- https://www.github.com/mbechler/marshalsec/blob/master/marshalsec.pdf?raw=true
- http://camel.apache.org/security-advisories.data/CVE-2016-8749.txt.asc?version=2&modificationDate=1486565034000&api=v2
- http://www.openwall.com/lists/oss-security/2017/05/22/2
- http://www.securityfocus.com/bid/97179
- https://github.com/apache/camel/commit/10f552643d7e4565104d142bbc160db5a30f9f7e
- https://github.com/apache/camel/commit/235036d2396ae45b6809b72a1983dee33b5ba326
- https://github.com/apache/camel/commit/2b0e96117d6f01eba0c18e2ff8df6a438e819721
- https://github.com/apache/camel/commit/57d01e2fc8923263df896e9810329ee5b7f9b69e
- https://github.com/apache/camel/commit/5ae9c0dcc4843347cd01ffb58ce5dd0687755a14
- https://github.com/apache/camel/commit/7567488f844f01d72840f7ab6ca18114a11f20d8
- https://github.com/apache/camel/commit/83fef7108456eeac1506853d194cd1360851c4fe
- https://github.com/apache/camel/commit/881e5099f94316d4a66ffbff0a3e6915829d49d7
- https://github.com/apache/camel/commit/8c862aa11e31d0f804c4a4516a0715e05e3eebcf
- https://github.com/apache/camel/commit/abb45b2c2ada2bbb34138230540b37d259c1e98d
- https://github.com/apache/camel/commit/ccf149c76bf37adc5977dc626e141a14e60b5aee
- https://github.com/apache/camel/commit/d4102512147eca2af21c3b6ed63a67d852f4e66a
- https://issues.apache.org/jira/browse/CAMEL-10567
- https://issues.apache.org/jira/browse/CAMEL-10604
- https://lists.apache.org/thread.html/2318d7f7d87724d8716cd650c21b31cb06e4d34f6d0f5ee42f28fdaf%40%3Ccommits.camel.apache.org%3E
- https://lists.apache.org/thread.html/b4014ea7c5830ca1fc28edd5cafedfe93ad4af2d9e69c961c5def31d%40%3Ccommits.camel.apache.org%3E
- http://camel.apache.org/security-advisories.data/CVE-2016-8749.txt.asc
- https://bugzilla.redhat.com/show_bug.cgi?id=1420832
Frequently Asked Questions
What is the severity of CVE-2016-8749?
CVE-2016-8749 is classified as a high-severity vulnerability due to its potential for remote code execution through deserialization of untrusted data.
How do I fix CVE-2016-8749?
To mitigate CVE-2016-8749, upgrade to Apache Camel versions 2.18.2, 2.17.5, or 2.16.5, which contain the necessary security fixes.
What components are affected by CVE-2016-8749?
CVE-2016-8749 affects the camel-jackson and camel-jacksonxml components of Apache Camel.
Can CVE-2016-8749 be exploited remotely?
Yes, CVE-2016-8749 can be exploited remotely if untrusted data is deserialized by vulnerable components.
What versions of Apache Camel are vulnerable to CVE-2016-8749?
Versions of Apache Camel prior to 2.18.2, 2.17.5, and 2.16.5 are vulnerable to CVE-2016-8749.
- collector/github-advisory-latest
- alias/GHSA-vvjc-q5vr-52q6
- alias/CVE-2016-8749
- collector/github-advisory
- agent/type
- agent/first-publish-date
- agent/softwarecombine
- agent/weakness
- agent/references
- agent/severity
- collector/redhat-bugzilla
- source/Red Hat
- agent/software-canonical-lookup
- agent/description
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/nvd-cve
- agent/software-canonical-lookup-request
- collector/nvd-index
- agent/author
- package-manager/maven
- package-manager/redhat
- vendor/apache
- canonical/red hat build of apache camel
- version/red hat build of apache camel/2.16.0
- version/red hat build of apache camel/2.16.1
- version/red hat build of apache camel/2.16.2
- version/red hat build of apache camel/2.16.3
- version/red hat build of apache camel/2.16.4
- version/red hat build of apache camel/2.17.0
- version/red hat build of apache camel/2.17.1
- version/red hat build of apache camel/2.17.2
- version/red hat build of apache camel/2.17.3
- version/red hat build of apache camel/2.17.4
- version/red hat build of apache camel/2.18.0
- version/red hat build of apache camel/2.18.1