CVE-2022-29240: Scylla is a real-time big data database that is API-compatible with Apache Cassandra and Amazon DynamoDB. When decompressing CQL frame received from u...

Description

Scylla is a real-time big data database that is API-compatible with Apache Cassandra and Amazon DynamoDB. When decompressing CQL frame received from user, Scylla assumes that user-provided uncompressed length is correct. If user provides fake length, that is greater than the real one, part of decompression buffer won't be overwritten, and will be left uninitialized. This can be exploited in several ways, depending on the privileges of the user. 1. The main exploit is that an attacker with access to CQL port, but no user account, can bypass authentication, but only if there are other legitimate clients making connections to the cluster, and they use LZ4. 2. Attacker that already has a user account on the cluster can read parts of uninitialized memory, which can contain things like passwords of other users or fragments of other queries / results, which leads to authorization bypass and sensitive information disclosure. The bug has been patched in the following versions: Scylla Enterprise: 2020.1.14, 2021.1.12, 2022.1.0. Scylla Open Source: 4.6.7, 5.0.3. Users unable to upgrade should make sure none of their drivers connect to cluster using LZ4 compression, and that Scylla CQL port is behind firewall. Additionally make sure no untrusted client can connect to Scylla, by setting up authentication and applying workarounds from previous point (firewall, no lz4 compression).

Metrics

CVSS 3.1

8.1/10

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Probability

0.94%

56.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-908

Affected Software

Vendor	Product	Versions
Scylladb	Scylla	< 4.6.7
Scylladb	Scylla	< 2020.1.14
Scylladb	Scylla	>= 5.0.0, < 5.0.3
Scylladb	Scylla	>= 2021.1.0, < 2021.1.12

References

https://github.com/scylladb/scylla/security/advisories/GHSA-25pq-rrqm-6fmrThird Party Advisory
https://github.com/scylladb/scylladb/commit/1c2eef384da439b0457b6d71c7e37d7268e471cbPatch, Third Party Advisory
https://github.com/scylladb/scylladb/issues/11476Issue Tracking, Patch, Third Party Advisory
https://github.com/scylladb/scylla/security/advisories/GHSA-25pq-rrqm-6fmrThird Party Advisory
https://github.com/scylladb/scylladb/commit/1c2eef384da439b0457b6d71c7e37d7268e471cbPatch, Third Party Advisory
https://github.com/scylladb/scylladb/issues/11476Issue Tracking, Patch, Third Party Advisory

Timeline

Published: Sep 15, 2022
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2022-29240?

Scylla is a real-time big data database that is API-compatible with Apache Cassandra and Amazon DynamoDB. When decompressing CQL frame received from user, Scylla assumes that user-provided uncompressed length is correct. If user provides fake length, that is greater than the real one, part of decompression buffer won't be overwritten, and will be left uninitialized. This can be exploited in several ways, depending on the privileges of the user. 1. The main exploit is that an attacker with access to CQL port, but no user account, can bypass authentication, but only if there are other legitimate clients making connections to the cluster, and they use LZ4. 2. Attacker that already has a user account on the cluster can read parts of uninitialized memory, which can contain things like passwords of other users or fragments of other queries / results, which leads to authorization bypass and sensitive information disclosure. The bug has been patched in the following versions: Scylla Enterprise: 2020.1.14, 2021.1.12, 2022.1.0. Scylla Open Source: 4.6.7, 5.0.3. Users unable to upgrade should make sure none of their drivers connect to cluster using LZ4 compression, and that Scylla CQL port is behind firewall. Additionally make sure no untrusted client can connect to Scylla, by setting up authentication and applying workarounds from previous point (firewall, no lz4 compression).

How severe is CVE-2022-29240?

CVE-2022-29240 has a CVSS score of 8.1/10 (HIGH severity). The EPSS model estimates a 0.94% probability of exploitation in the next 30 days.

How do I fix CVE-2022-29240?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.