Skip to content
Fencer Intel
critical 9.8

CVE-2020-11972 json

Deserialization of Untrusted Data in Apache Camel RabbitMQ

published 6y ago modified 4mo ago also GHSA-2x6r-7427-95cm , EUVD-2021-0910

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

Summary

Apache Camel RabbitMQ enables Java deserialization by default. Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to 3.1.0 are affected. 2.x users should upgrade to 2.25.1, 3.x users should upgrade to 3.2.0.

Patch / fix

  • maven org.apache.camel:camel-rabbitmq 2.25.1, 3.2.0

Is CVE-2020-11972 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-2020-11972 updated cvss 9.8

camel: RabbitMQ enables Java deserialization by default which could leed to remote code execution

  • Red Hat JBoss Fuse 6 camel-rabbitmq camel-rabbitmq
    affected: no fix available
  • Red Hat Fuse 7.8.0
    fixed: vendor fix RHSA-2020:5568
  • Red Hat JBoss Data Grid 7 camel-rabbitmq camel-rabbitmq
    not affected: vulnerable code not present

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

5.65% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/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.1 9.8 CVSS:3.1/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-rabbitmq
<2.25.1
>=3.0.0, <3.2.0
2.25.1
3.2.0

Affected products

  • n/a 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.