# CVE-2020-1954: Apache CXF JMX Integration is vulnerable to a MITM attack

> An attacker on the same host can intercept JMX communications via a man-in-the-middle attack if the default connector factory is enabled, exposing sensitive data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-ffm7-7r8g-77xm

## What is CVE-2020-1954?

CVE-2020-1954 is a medium-severity vulnerability in Apache Cxf, published on 1 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Apache CXF has the ability to integrate with JMX by registering an InstrumentationManager extension with the CXF bus. If the ‘createMBServerConnectorFactory‘ property of the default InstrumentationManagerImpl is not disabled, then it is vulnerable to a man-in-the-middle (MITM) style attack. An attacker on the same host can connect to the registry and rebind the entry to another server, thus acting as a proxy to the original. They are then able to gain access to all of the information that is sent and received over JMX.

## Which versions are affected by CVE-2020-1954?

4 open source packages ship an affected version, including org.apache.cxf:cxf-rt-management. It affects 10 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.cxf:cxf-rt-management` | Maven | All versions | 3.2.13 |
| `org.apache.cxf:cxf-rt-management` | Maven | All versions | 3.2.13 |
| `org.apache.cxf:cxf-rt-management` | Maven | From 3.3.0 | 3.3.6 |
| `org.apache.cxf:cxf-rt-management` | Maven | From 3.3.0 | 3.3.6 |

Products: Apache Cxf, Netapp Oncommand Workflow Automation, Netapp Snapmanager, Oracle Communications Diameter Signaling Router, Oracle Communications Diameter Signaling Router Idih\, Oracle Communications Element Manager, Oracle Communications Session Report Manager, Oracle Communications Session Route Manager, Oracle Enterprise Manager Base Platform, Oracle Peoplesoft Enterprise Peopletools.

## How do I fix CVE-2020-1954?

Upgrade org.apache.cxf:cxf-rt-management to a fixed version for your release line: 3.2.13 or 3.3.6.

## Is CVE-2020-1954 being exploited?

There is no known exploitation of CVE-2020-1954 in the wild and no public exploit code.

## Other vulnerabilities in Apache Cxf

- [CVE-2012-2379](https://insights.sbomify.com/CVE-2012-2379/): XML Signature/Encryption Not Validated in Apache CXF (critical 10.0)
- [CVE-2026-66909](https://insights.sbomify.com/CVE-2026-66909/): Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage (critical 9.8)
- [CVE-2026-68079](https://insights.sbomify.com/CVE-2026-68079/): Apache CXF: DefaultEncryptingCodeDataProvider allows unlimited authorization code replay (critical 9.8)
- [CVE-2026-50628](https://insights.sbomify.com/CVE-2026-50628/): Apache CXF: OAuth2: Inverted IP Binding Check Defeats Security Control (critical 9.8)
- [CVE-2025-48913](https://insights.sbomify.com/CVE-2025-48913/): Apache CXF: Untrusted JMS configuration can lead to RCE (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1954 and fix it if it is affected.

What it is: CVE-2020-1954 is a medium-severity vulnerability in Apache Cxf, published on 1 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-1954 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.cxf:cxf-rt-management (Maven): affected all versions; fixed in 3.2.13
- org.apache.cxf:cxf-rt-management (Maven): affected all versions; fixed in 3.2.13
- org.apache.cxf:cxf-rt-management (Maven): affected from 3.3.0; fixed in 3.3.6
- org.apache.cxf:cxf-rt-management (Maven): affected from 3.3.0; fixed in 3.3.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-1954/ (Markdown: https://insights.sbomify.com/CVE-2020-1954/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-1954
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-1954
- OSV: https://osv.dev/vulnerability/CVE-2020-1954

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-1954/
Summaries are generated and may contain mistakes; the official description above is the record.