Uninitialized memory read in LZ4 decompression leads to authentication bypass in Scylla
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
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).
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| scylladb | scylla | before 4.6.7; 5.0.0 to before 5.0.3 | 4.6.7, 5.0.3 | Patch available | CNA |
- scylla Vendorscylladb Affected before 4.6.7; 5.0.0 to before 5.0.3 Fixed in 4.6.7, 5.0.3 Patch available CNA
CPE configurations NVD · 4
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:scylladb:scylla:*:*:*:*:open_source:*:*:* | before 4.6.7 | Vulnerable | scylladb |
| cpe:2.3:a:scylladb:scylla:*:*:*:*:enterprise:*:*:* | before 2020.1.14 | Vulnerable | scylladb |
| cpe:2.3:a:scylladb:scylla:*:*:*:*:open_source:*:*:* | 5.0.0 to before 5.0.3 | Vulnerable | scylladb |
| cpe:2.3:a:scylladb:scylla:*:*:*:*:enterprise:*:*:* | 2021.1.0 to before 2021.1.12 | Vulnerable | scylladb |
- cpe:2.3:a:scylladb:scylla:*:*:*:*:open_source:*:*:* Versions before 4.6.7 Vulnerable ·scylladb
- cpe:2.3:a:scylladb:scylla:*:*:*:*:enterprise:*:*:* Versions before 2020.1.14 Vulnerable ·scylladb
- cpe:2.3:a:scylladb:scylla:*:*:*:*:open_source:*:*:* Versions 5.0.0 to before 5.0.3 Vulnerable ·scylladb
- cpe:2.3:a:scylladb:scylla:*:*:*:*:enterprise:*:*:* Versions 2021.1.0 to before 2021.1.12 Vulnerable ·scylladb
Remediation
- Fix · CNA scylla (scylladb) Fixed in 4.6.7, 5.0.3
Timeline
- 2026-10-02 Threatist record created from CVE-2022-29240
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences