CVE Vulnerabilities

CVE-2020-13946

Exposure of Resource to Wrong Sphere

Published: Sep 01, 2020 | Modified: Nov 07, 2023
CVSS 3.x
5.9
MEDIUM
Source:
NVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 2.x
4.3 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N
RedHat/V2
RedHat/V3
5.9 MODERATE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Ubuntu

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

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

Affected Software

Name Vendor Start Version End Version
Cassandra Apache * 2.1.22 (excluding)
Cassandra Apache 2.2.0 (including) 2.2.18 (excluding)
Cassandra Apache 3.0.0 (including) 3.0.22 (excluding)
Cassandra Apache 3.11.0 (including) 3.11.8 (excluding)
Cassandra Apache 4.0.0-alpha1 (including) 4.0.0-alpha1 (including)
Cassandra Apache 4.0.0-alpha2 (including) 4.0.0-alpha2 (including)
Cassandra Apache 4.0.0-alpha3 (including) 4.0.0-alpha3 (including)
Cassandra Apache 4.0.0-alpha4 (including) 4.0.0-alpha4 (including)
Cassandra Apache 4.0.0-beta1 (including) 4.0.0-beta1 (including)
Red Hat Integration - Camel K - Tech-Preview 3 RedHat cassandra *

Extended Description

Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files. A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system. In either case, the end result is that a resource has been exposed to the wrong party.

References