CVE-2020-11971Network attack vector

Information disclosure via unsecured JMX registry rebind

Published May 14, 2020 · Updated Aug 4, 2024

Information disclosure in Apache Camel JMX 2.22.x through 2.25.0 and 3.0.0 through 3.1.0 allows remote attackers to read sensitive data. The camel-management JMX connector creates its own RMI registry, whose existing binding remote clients can replace because the registry is not properly secured. Exploitation requires the optional camel-management JAR and a remotely reachable JMX connector; a successful rebind can redirect management clients and expose sensitive information.

CVSS severity7.5
High
EPSS probability13.96%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Information disclosure in Apache Camel JMX 2.22.x through 2.25.0 and 3.0.0 through 3.1.0 allows remote attackers to read sensitive data. The camel-management JMX connector creates its own RMI registry, whose existing binding remote clients can replace because the registry is not properly secured. Exploitation requires the optional camel-management JAR and a remotely reachable JMX connector; a successful rebind can redirect management clients and expose sensitive information.

The record

CVE
CVE-2020-11971
Published
May 14, 2020
Updated
Aug 4, 2024
Vendor
The Apache Software Foundation
Product
Apache Camel
Classifications
T1557
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 14, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to 3.1.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

The Apache Software Foundation · Apache Camelversion=Apache Camel 2.22.x, 2.23.x, 2.24.x, 2.25.0, 3.0.0 up to 3.1.0

Published CVSS scores

5.0NIST NVDAV:N/AC:L/Au:N/C:P/I:N/A:N
7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1557Adversary-in-the-Middle

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo