{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15024 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15024 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15024 is a medium-severity path traversal vulnerability in ClickHouse, published on 30 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-15024 and fix it if it is affected.\n\nWhat it is: CVE-2019-15024 is a medium-severity path traversal vulnerability in ClickHouse, published on 30 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-15024 in the wild and no public exploit code.\n\nAffected product: ClickHouse. 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-2019-15024/ (Markdown: https://insights.sbomify.com/CVE-2019-15024/index.md)","id":"CVE-2019-15024","markdown":"https://insights.sbomify.com/CVE-2019-15024/index.md","name":"CVE-2019-15024","record":{"aliases":["GHSA-vv4f-6f99-x599"],"analysis":{"component_type":"database","fix_type":"upgrade","impacts":["data_modify","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"ClickHouse database","requires_auth":"low_privilege","summary":"An attacker with ZooKeeper write access can force ClickHouse replicas to write files to arbitrary filesystem paths, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"yandex","cpe":[{"product":"clickhouse","vendor":"clickhouse"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"In all versions of ClickHouse before 19.14.3, an attacker having write access to ZooKeeper and who is able to run a custom server available from the network where ClickHouse runs, can create a custom-built malicious server that will act as a ClickHouse replica and register it in ZooKeeper. When another replica will fetch data part from the malicious replica, it can force clickhouse-server to write to arbitrary path on filesystem.","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":"Path traversal in ClickHouse","id":"CVE-2019-15024","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2019-15025"},"packages":[],"prev":{"headline":"Information disclosure in Palo Alto Networks Zingbox Inspector","id":"CVE-2019-15023"},"products":["ClickHouse"],"published":"2019-12-30","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker with ZooKeeper write access can force ClickHouse replicas to write files to arbitrary filesystem paths, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2019-15024/"}