{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-44010 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-44010 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-44010 is a high-severity memory corruption vulnerability in n/a, published on 23 Nov 2023. 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-44010 and fix it if it is affected.\n\nWhat it is: CVE-2022-44010 is a high-severity memory corruption vulnerability in n/a, published on 23 Nov 2023. 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-44010 in the wild and no public exploit code.\n\nAffected product: n/a. 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-44010/ (Markdown: https://insights.sbomify.com/CVE-2022-44010/index.md)","id":"CVE-2022-44010","markdown":"https://insights.sbomify.com/CVE-2022-44010/index.md","name":"CVE-2022-44010","record":{"aliases":["DEBIAN-CVE-2022-44010","ECHO-cf7f-65c8-584d","GHSA-jf32-cfwc-7953","UBUNTU-CVE-2022-44010"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"ClickHouse database","requires_auth":"none","summary":"Unauthenticated attackers can crash the ClickHouse database process via a heap-based buffer overflow in the HTTP endpoint.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"clickhouse","vendor":"clickhouse"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"An issue was discovered in ClickHouse before 22.9.1.2603. An attacker could send a crafted HTTP request to the HTTP Endpoint (usually listening on port 8123 by default), causing a heap-based buffer overflow that crashes the process. This does not require authentication. The fixed versions are 22.9.1.2603, 22.8.2.11, 22.7.4.16, 22.6.6.16, and 22.3.12.19.","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":"Memory corruption in n/a","id":"CVE-2022-44010","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2022-44011"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2022-44009"},"products":["n/a"],"published":"2023-11-23","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-03","vendors":["n/a"]},"summary":"Unauthenticated attackers can crash the ClickHouse database process via a heap-based buffer overflow in the HTTP endpoint.","url":"https://insights.sbomify.com/CVE-2022-44010/"}