Skip to content
Fencer Intel
critical 9.8

CVE-2017-12633 json

Apache Camel camel-hessian component vulnerable to Java object deserialization

published 2017-11-15 8 y ago modified 2026-06-17 4 mo ago also GHSA-5whj-523x-6j68 , EUVD-2022-2668

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-hessian 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-hessian 2.19.4, 2.20.1
  • apache camel 2.19.4, 2.20.1

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-12633 updated cvss 7.5

camel-hessian: Apache Camel's Hessian unmarshalling operation is vulnerable to Remote Code Execution attacks

  • Red Hat JBoss Fuse 6 Camel Camel
    affected: no fix planned “Out of support scope”
  • Red Hat JBoss A-MQ 6.3 Red Hat JBoss Fuse 6.3
    fixed: 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-09).

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-hessian
>=2.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

Sources

Fencer Intel 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.