Skip to content

Cassandra-Lucene-Index allows bypass of Cassandra RBAC

High
aleks-instaclustr published GHSA-mrqp-q7vx-v2cx Feb 13, 2025

Package

No package listed

Affected versions

>=4.0-rc1-1.0.0
>=4.1.0-1.0.0

Patched versions

4.0.17-1.0.0
4.1.8-1.0.1

Description

Summary / Details
Systems running the Instaclustr fork of Stratio's Cassandra-Lucene-Index plugin versions 4.0-rc1-1.0.0 through 4.0.16-1.0.0 and 4.1.0-1.0.0 through 4.1.8-1.0.0, installed into Apache Cassandra version 4.x, are susceptible to a vulnerability which when successfully exploited could allow authenticated Cassandra users to remotely bypass RBAC to access data and and escalate their privileges.

Affected Versions

  • Cassandra-Lucene-Index plugin versions 4.0-rc1-1.0.0 through 4.0.16-1.0.0
  • versions 4.1.0-1.0.0 through 4.1.8-1.0.0
    when installed into Apache Cassandra version 4.x.

Required Configuration for Exploit
These are the conditions required to enable exploit:

  1. Cassandra 4.x
  2. Vulnerable version of the Cassandra-Lucene-Index plugin configured for use
  3. Data added to tables
  4. Lucene index created
  5. Cassandra flush has run

Mitigation/Prevention
Mitigation requires dropping all Lucene indexes and stopping use of the plugin. Exploit will be possible any time the required conditions are met.

Solution
Upgrade to a fixed version of the Cassandra-Lucene-Index plugin.
Review users in Cassandra to validate all superuser privileges.

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVE ID

CVE-2025-26511

Weaknesses

Credits