{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-42387 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2021-42387 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 14 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-42387 and fix it if it is affected.\n\nWhat it is: CVE-2021-42387 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 14 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-42387 in the wild and no public exploit code.\n\nAffected product: Debian Debian Linux. 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-2021-42387/ (Markdown: https://insights.sbomify.com/CVE-2021-42387/index.md)","id":"CVE-2021-42387","markdown":"https://insights.sbomify.com/CVE-2021-42387/index.md","name":"CVE-2021-42387","record":{"aliases":["DEBIAN-CVE-2021-42387","GHSA-cf9g-639p-3wvv","UBUNTU-CVE-2021-42387"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ClickHouse database","requires_auth":"low_privilege","summary":"An attacker can trigger a heap out-of-bounds read in ClickHouse via a malicious query, potentially causing a crash or leaking memory.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"JFROG","cpe":[{"product":"clickhouse","vendor":"clickhouse"},{"product":"debian_linux","vendor":"debian"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"Heap out-of-bounds read in Clickhouse's LZ4 compression codec when parsing a malicious query. As part of the LZ4::decompressImpl() loop, a 16-bit unsigned user-supplied value ('offset') is read from the compressed data. The offset is later used in the length of a copy operation, without checking the upper bounds of the source of the copy operation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Memory corruption in clickhouse","id":"CVE-2021-42387","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux"],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in clickhouse","id":"CVE-2021-42388"},"packages":[],"prev":{"headline":"Use after free in busybox","id":"CVE-2021-42386"},"products":["clickhouse"],"published":"2022-03-14","related":[{"cvss_score":9.8,"headline":"Memory corruption in ClickHouse","id":"CVE-2019-16535","kev_date_added":null,"published":"2019-12-30"},{"cvss_score":9.8,"headline":"Missing authorization in ClickHouse","id":"CVE-2018-14670","kev_date_added":null,"published":"2019-08-15"},{"cvss_score":9.8,"headline":"Code injection in ClickHouse","id":"CVE-2018-14671","kev_date_added":null,"published":"2019-08-15"},{"cvss_score":8.8,"headline":"Memory corruption in clickhouse","id":"CVE-2021-43304","kev_date_added":null,"published":"2022-03-14"},{"cvss_score":8.8,"headline":"Memory corruption in clickhouse","id":"CVE-2021-43305","kev_date_added":null,"published":"2022-03-14"},{"cvss_score":8.8,"headline":"Server-side request forgery in ClickHouse","id":"CVE-2018-14668","kev_date_added":null,"published":"2019-08-15"},{"cvss_score":8.2,"headline":"Stack overflow leading to DoS can be triggered by a malicious authenticated client.","id":"CVE-2019-16536","kev_date_added":null,"published":"2025-05-21"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["yandex"]},"summary":"An attacker can trigger a heap out-of-bounds read in ClickHouse via a malicious query, potentially causing a crash or leaking memory.","url":"https://insights.sbomify.com/CVE-2021-42387/"}