CVE-2020-11971: Input Validation

Published May 14, 2020
·
Updated

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.

Affected Software

11 affected componentsFixes available
Apache Camel>=2.22.0<=3.1.0
Oracle Communications Diameter Intelligence Hub>=8.0.0<=8.1.0
Oracle Communications Diameter Intelligence Hub>=8.2.0<=8.2.3
Oracle Communications Diameter Signaling Router>=8.0.0<=8.2.2
Oracle Enterprise Manager Base Platform=13.3.0.0
Oracle Enterprise Manager Base Platform=13.4.0.0
Oracle FLEXCUBE Private Banking=12.0.0
Oracle FLEXCUBE Private Banking=12.1.0
redhat/camel<3.2.0
3.2.0
IBM Engineering Requirements Management DOORS and DOORS Web Access<=9.7.2.1 - 9.7.2.11
IBM Engineering Requirements Management DOORS and DOORS Web Access<=9.6.1.1 - 9.6.1.13

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/camel to a version that resolves this vulnerability.

    Fixed in 3.2.0
  2. Upgrade

    Upgrade Apache Camel to a version that resolves this vulnerability.

    Fixed in 3.2.0
  3. Configuration

    Disable Apache Camel JMX by setting the Java system property -Dorg.apache.camel.jmx.disabled=true.

    Apache Camel JMX -Dorg.apache.camel.jmx.disabled = true
  4. Configuration

    Disable the vulnerable JMX agent by calling camel.disableJMX() on the CamelContext (if using the CamelContext method).

    Apache Camel CamelContext disableJMX() = called
  5. Configuration

    If using Spring, disable the vulnerable JMX instrumentation agent in the Camel configuration by setting <jmxAgent id="agent" disabled="true"/> inside the <camelContext>.

    Apache Camel Spring configuration (camelContext) <jmxAgent disabled> = true

Event History

May 14, 2020
CVE Published
12:00 AM
Data Sourced
12:00 AM
RemedyDescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·04:18 PM
Data Sourced
via MITRE·04:18 PM
DescriptionWeakness
Jun 18, 2020
Data Sourced
via Red Hat·11:19 AM
DescriptionSeverityAffected Software
Jul 6, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2020-11971?

CVE-2020-11971 is a vulnerability in Apache Camel's JMX that allows for a rebind flaw.

2

What versions of Apache Camel are affected by CVE-2020-11971?

Apache Camel versions 2.22.x, 2.23.x, 2.24.x, 2.25.x, and 3.0.0 up to 3.1.0 are affected by CVE-2020-11971.

3

How severe is CVE-2020-11971?

CVE-2020-11971 has a severity rating of 7.5 (high).

4

How can I fix CVE-2020-11971?

To fix CVE-2020-11971, users should upgrade to Apache Camel version 3.2.0.

5

Where can I find more information about CVE-2020-11971?

You can find more information about CVE-2020-11971 on the CVE website (https://www.cve.org/CVERecord?id=CVE-2020-11971) and the NVD website (https://nvd.nist.gov/vuln/detail/CVE-2020-11971).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203