Skip to content
Fencer Intel
critical 9.8

CVE-2015-5344 json

Camel-xstream component in Apache Camel can allow remote attackers to execute arbitrary commands

published 10y ago modified 4mo ago also GHSA-gv5f-cjw9-5vxg , EUVD-2018-0605

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.1%
EPSS 7.1% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

The camel-xstream component in Apache Camel before 2.15.5 and 2.16.x before 2.16.1 allow remote attackers to execute arbitrary commands via a crafted serialized Java object in an HTTP request.

Patch / fix

  • maven org.apache.camel:camel-xstream 2.15.5, 2.16.1

Is CVE-2015-5344 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2015-5344 updated cvss 4.2

camel-xstream: Java object de-serialization vulnerability leads to RCE

  • Red Hat OpenShift Enterprise 1 camel Red Hat JBoss BRMS 5 camel
    affected: no fix planned “Will not fix”
  • Red Hat JBoss Fuse 6 camel Red Hat JBoss Fuse Service Works 6 camel Red Hat OpenShift Enterprise 2 camel
    affected: no fix available
  • Red Hat JBoss Fuse 6.3
    fixed: vendor fix RHSA-2016:2035

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.12% 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-xstream
<2.15.5
>=2.16.0, <2.16.1
2.15.5
2.16.1

Classification

Weakness
  • CWE-19 Data Processing Errors

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.