{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-29240 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-29240 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-29240 is a high-severity authentication bypass vulnerability in scylladb scylla, published on 15 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-29240 and fix it if it is affected.\n\nWhat it is: CVE-2022-29240 is a high-severity authentication bypass vulnerability in scylladb scylla, published on 15 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-29240 in the wild and no public exploit code.\n\nAffected product: scylladb scylla. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-29240/ (Markdown: https://insights.sbomify.com/CVE-2022-29240/index.md)","id":"CVE-2022-29240","markdown":"https://insights.sbomify.com/CVE-2022-29240/index.md","name":"CVE-2022-29240","record":{"aliases":["GHSA-25pq-rrqm-6fmr"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Scylla database","requires_auth":"none","summary":"Attackers can bypass authentication or read sensitive memory in Scylla database if LZ4 compression is used, requiring upgrades or disabling compression.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"scylla","vendor":"scylladb"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Uninitialized memory read in LZ4 decompression leads to authentication bypass in Scylla","id":"CVE-2022-29240","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Known or guessable hidden files may be accessed in Jupyter Server","id":"CVE-2022-29241"},"packages":[],"prev":{"headline":"Forced Browsing in Jupyter Notebook","id":"CVE-2022-29238"},"products":["scylla"],"published":"2022-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["scylladb"]},"summary":"Attackers can bypass authentication or read sensitive memory in Scylla database if LZ4 compression is used, requiring upgrades or disabling compression.","url":"https://insights.sbomify.com/CVE-2022-29240/"}