Skip to content
Fencer Intel
high 7.5

CVE-2020-11971 in the critical feed json

Improper Input Validation in Apache Camel

published 6y ago modified last mo. also GHSA-hfg5-xpvw-c9x4 , EUVD-2021-1101

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

Summary

Apache Camel's JMX is vulnerable to Rebind Flaw. Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.x, 3.0.0 up to 3.1.0 is affected. Users should upgrade to 3.2.0.

Patch / fix

  • maven org.apache.camel:camel 3.2.0
  • maven org.apache.camel:camel-core 3.2.0
  • maven org.apache.camel:camel-management 3.2.0

Is CVE-2020-11971 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-11971 updated cvss 7.5

camel: DNS Rebinding in JMX Connector could result in remote command execution

  • Red Hat JBoss Data Grid 7 camel-core
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Fuse 7.8.0
    fixed: vendor fix RHSA-2020:5568

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

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

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.camel:camel
<3.2.0
3.2.0
maven org.apache.camel:camel-core
<3.2.0
3.2.0
maven org.apache.camel:camel-management
<3.2.0
3.2.0

Affected products

  • n/a Apache Camel

Classification

Weakness
  • CWE-20 Improper Input Validation

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.