CVE-2020-11971 is a high-severity (CVSS 7.5) vulnerability in org.apache.camel:camel. EPSS puts its 30-day exploitation probability at 14.0% (97th percentile). A fix is available for org.apache.camel:camel — see the affected versions and patch details below.
Improper Input Validation in Apache Camel
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.apache.camel:camel☕org.apache.camel:camel-core☕org.apache.camel:camel-managementReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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 Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.camel:camel | all versions | 3.2.0org.apache.camel:camel:3.2.0 |
| ☕Maven | org.apache.camel:camel-core | all versions | 3.2.0org.apache.camel:camel-core:3.2.0 |
| ☕Maven | org.apache.camel:camel-management | all versions | 3.2.0org.apache.camel:camel-management:3.2.0 |
Affected Products
camelapachecommunications diameter intelligence huboraclecommunications diameter signaling routeroracleenterprise manager base platformoracleflexcube private bankingoracleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.camel:camel to 3.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-11971 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
The JMX instrumentation agent is the vulnerable component in this, if not being used it can be disabled in the following ways * As a Java system property - `-Dorg.apache.camel.jmx.disabled=true` as java system property * Using the CamelContext method - ```java CamelContext camel = new DefaultCamelContext(); camel.disableJMX(); ``` * If using spring altering the spring configuration - ```xml <camelContext id="camel" xmlns="http://camel.apache.org/schema/spring"> <jmxAgent id="agent" disabled="true"/> ... </camelContext> ```Source: Red Hat security advisory for CVE-2020-11971 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Fuse 7.8.0 | camel-core | RHSA-2020:5568 |
Frequently Asked Questions
Is CVE-2020-11971 in your dependencies?
Find it across Maven, including transitive dependencies.