CVE-2017-12634 json
Camel-castor component in Apache Camel is vulnerable to Java object de-serialisation
published 2017-11-15 8 y ago modified 2026-06-17 4 mo ago also GHSA-vf4q-8mr7-5c5c , EUVD-2018-0695
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.2%
- EPSS 7.2% chance of exploitation in 30 days, percentile 94%
- public exploits
- 0
- none known
Summary
The camel-castor component in Apache Camel 2.x before 2.19.4 and 2.20.x before 2.20.1 is vulnerable to Java object de-serialisation vulnerability. De-serializing untrusted data can lead to security flaws.
Patch / fix
- maven org.apache.camel:camel-castor 2.19.4, 2.20.1
- apache camel 2.19.4
- github.com/apache/camel@2ae645e commit
- github.com/apache/camel@573ebd3 commit
- github.com/apache/camel@ad3c1ce commit
- github.com/apache/camel@adc06a7 commit
- github.com/apache/camel@bdff8f3 commit
- github.com/apache/camel@c613905 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2017-12634 updated cvss 7.5
camel-castor: Apache Camel's Castor unmarshalling operation is vulnerable to Remote Code Execution attacks
-
Red Hat JBoss Fuse 6 camel-castor camel-castoraffected: no fix available
-
Red Hat JBoss Fuse Service Works 6 camel-castor camel-castoraffected: no fix planned “Out of support scope”
-
Red Hat JBoss A-MQ 6.3 Red Hat JBoss Fuse 6.3fixed: vendor fix RHSA-2018:0319
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
7.19% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
| GitHub | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.camel:camel-castor | >=2.0.0, <2.19.4 >=2.20.0, <2.20.1 |
2.19.4 2.20.1 |
Affected products
- Apache Software Foundation Apache Camel
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/apache/camel/commit/2ae645e90edff3bcc1b958cb53ddc5e60a7f49fd
web
-
github.com
/apache/camel/commit/573ebd3de810cc7e239f175e1d2d6993f1f2ad08
web
-
github.com
/apache/camel/commit/ad3c1ce9d8300c339cfa7d0f4a4dea691a947988
web
-
github.com
/apache/camel/commit/adc06a78f04c8d798709a5818104abe5a8ae4b38
web
-
github.com
/apache/camel/commit/bdff8f3f3583e4f14cdaf24f2037e0fbef252630
web
-
github.com
/apache/camel/commit/c613905e95a3dab87158d9526aea9439f2de9621
web
-
access.redhat.com
/errata/RHSA-2018:0319
vendor-advisory, web, third-party-advisory
-
issues.apache.org
/jira/browse/CAMEL-11929
web, issue-tracking, vendor-advisory
-
camel.apache.org
/security-advisories.data/CVE-2017-12634.txt.asc
web, issue-tracking, vendor-advisory
-
securityfocus.com
/bid/101876
vdb-entry, web, issue-tracking, third-party-advisory
-
lists.apache.org
/thread.html/b4014ea7c5830ca1fc28edd5cafedfe93ad4af2d9e69c961c5def31d%40%3Ccommits.camel.apache.org%3E
mailing-list
-
lists.apache.org
/thread.html/2318d7f7d87724d8716cd650c21b31cb06e4d34f6d0f5ee42f28fdaf%40%3Ccommits.camel.apache.org%3E
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2017-12634
advisory
-
github.com
/advisories/GHSA-vf4q-8mr7-5c5c
advisory
-
github.com
/apache/camel
package
-
lists.apache.org
/thread.html/2318d7f7d87724d8716cd650c21b31cb06e4d34f6d0f5ee42f28fdaf@%3Ccommits.camel.apache.org%3E
web
-
lists.apache.org
/thread.html/b4014ea7c5830ca1fc28edd5cafedfe93ad4af2d9e69c961c5def31d@%3Ccommits.camel.apache.org%3E
web
Sources
- CVE List CVE-2017-12634
- GitHub Advisory GHSA-vf4q-8mr7-5c5c
- NVD CVE-2017-12634
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.