# CVE-2020-13946: Man-in-the-middle attack in Apache Cassandra > Local attackers can intercept JMX credentials via RMI manipulation, enabling unauthorized access to the database interface. - **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/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:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 1 Sep 2020 - **Updated:** 4 Aug 2024 - **Also known as:** BIT-cassandra-2020-13946, GHSA-24ww-mc5x-xc43 ## What is CVE-2020-13946? CVE-2020-13946 is a medium-severity vulnerability in Netapp Oncommand Insight, published on 1 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description In Apache Cassandra, all versions prior to 2.1.22, 2.2.18, 3.0.22, 3.11.8 and 4.0-beta2, it is possible for a local attacker without access to the Apache Cassandra process or configuration files to manipulate the RMI registry to perform a man-in-the-middle attack and capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and perform unauthorised operations. Users should also be aware of CVE-2019-2684, a JRE vulnerability that enables this issue to be exploited remotely. Weakness: CWE-668 (Exposure of Resource to Wrong Sphere) ## Which versions are affected by CVE-2020-13946? 11 open source packages ship an affected version, including org.apache.cassandra:cassandra-all and cassandra. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.cassandra:cassandra-all` | Maven | From 2.1.0 | 2.1.12 | | `org.apache.cassandra:cassandra-all` | Maven | From 2.1.0 | 2.1.12 | | `org.apache.cassandra:cassandra-all` | Maven | From 2.2.0 | 2.2.18 | | `org.apache.cassandra:cassandra-all` | Maven | From 2.2.0 | 2.2.18 | | `org.apache.cassandra:cassandra-all` | Maven | From 3.0.0 | 3.0.22 | | `org.apache.cassandra:cassandra-all` | Maven | From 3.0.0 | 3.0.22 | | `org.apache.cassandra:cassandra-all` | Maven | From 3.11.0 | 3.11.8 | | `org.apache.cassandra:cassandra-all` | Maven | From 3.11.0 | 3.11.8 | | `org.apache.cassandra:cassandra-all` | Maven | From 4.0-beta1 | 4.0-beta2 | | `org.apache.cassandra:cassandra-all` | Maven | From 4.0-beta1 | 4.0-beta2 | | `cassandra` | Bitnami | All versions | 2.1.22, 2.2.18, 3.0.22, 3.11.8 | Products: Apache Cassandra, Netapp Oncommand Insight. ## How do I fix CVE-2020-13946? Upgrade org.apache.cassandra:cassandra-all to a fixed version for your release line: 2.1.12, 2.2.18, 3.0.22 or 3.11.8. ## Is CVE-2020-13946 being exploited? There is no known exploitation of CVE-2020-13946 in the wild and no public exploit code. ## Other vulnerabilities in Netapp Oncommand Insight - [CVE-2016-3427](https://insights.sbomify.com/CVE-2016-3427/): Oracle Java SE and JRockit Unspecified (critical 9.8, exploited in the wild) - [CVE-2018-8016](https://insights.sbomify.com/CVE-2018-8016/): Missing Authentication for Critical Function in Apache Cassandra (critical 9.8) - [CVE-2021-44521](https://insights.sbomify.com/CVE-2021-44521/): Remote code execution for scripted UDFs (critical 9.1) - [CVE-2026-27314](https://insights.sbomify.com/CVE-2026-27314/): Apache Cassandra: Privilege escalation via ADD IDENTITY authorization bypass (high 8.8) - [CVE-2025-26467](https://insights.sbomify.com/CVE-2025-26467/): Apache Cassandra: User with MODIFY permission on ALL KEYSPACES can escalate privileges to superuser via unsafe actions (4.0.16 only) (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-13946 and fix it if it is affected. What it is: CVE-2020-13946 is a medium-severity vulnerability in Netapp Oncommand Insight, published on 1 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-13946 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.cassandra:cassandra-all (Maven): affected from 2.1.0; fixed in 2.1.12 - org.apache.cassandra:cassandra-all (Maven): affected from 2.1.0; fixed in 2.1.12 - org.apache.cassandra:cassandra-all (Maven): affected from 2.2.0; fixed in 2.2.18 - org.apache.cassandra:cassandra-all (Maven): affected from 2.2.0; fixed in 2.2.18 - org.apache.cassandra:cassandra-all (Maven): affected from 3.0.0; fixed in 3.0.22 - org.apache.cassandra:cassandra-all (Maven): affected from 3.0.0; fixed in 3.0.22 - org.apache.cassandra:cassandra-all (Maven): affected from 3.11.0; fixed in 3.11.8 - org.apache.cassandra:cassandra-all (Maven): affected from 3.11.0; fixed in 3.11.8 - org.apache.cassandra:cassandra-all (Maven): affected from 4.0-beta1; fixed in 4.0-beta2 - org.apache.cassandra:cassandra-all (Maven): affected from 4.0-beta1; fixed in 4.0-beta2 - cassandra (Bitnami): affected all versions; fixed in 2.1.22, 2.2.18, 3.0.22, 3.11.8 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-13946/ (Markdown: https://insights.sbomify.com/CVE-2020-13946/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-13946 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-13946 - OSV: https://osv.dev/vulnerability/CVE-2020-13946 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-13946/ Summaries are generated and may contain mistakes; the official description above is the record.