{"answers":{"affected":"3 open source packages ship an affected version, including org.apache.solr:solr-core and solr. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-52012 in the wild and no public exploit code.","fix":"Upgrade org.apache.solr:solr-core to 9.8.0 or later.","what":"CVE-2024-52012 is a medium-severity path traversal vulnerability in Apache Solr, published on 27 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-52012 and fix it if it is affected.\n\nWhat it is: CVE-2024-52012 is a medium-severity path traversal vulnerability in Apache Solr, published on 27 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-52012 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.solr:solr-core (Maven): affected from 6.6; fixed in 9.8.0\n- org.apache.solr:solr-core (Maven): affected from 6.6; fixed in 9.8.0\n- solr (Bitnami): affected from 6.6.0; fixed in 9.8.0\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-2024-52012/ (Markdown: https://insights.sbomify.com/CVE-2024-52012/index.md)","id":"CVE-2024-52012","markdown":"https://insights.sbomify.com/CVE-2024-52012/index.md","name":"CVE-2024-52012","record":{"aliases":["BIT-solr-2024-52012","GHSA-4p5m-gvpf-f3x5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Solr search engine","requires_auth":"low_privilege","summary":"Attackers can write arbitrary files to the filesystem on Windows via malicious ZIP uploads in the configset API, requiring an upgrade to fix.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"solr","vendor":"apache"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-23","name":"Relative Path Traversal"}],"description":"Relative Path Traversal vulnerability in Apache Solr.\n\nSolr instances running on Windows are vulnerable to arbitrary filepath write-access, due to a lack of input-sanitation in the \"configset upload\" API.  Commonly known as a \"zipslip\", maliciously constructed ZIP files can use relative filepaths to write data to unanticipated parts of the filesystem.  \nThis issue affects Apache Solr: from 6.6 through 9.7.0.\n\nUsers are recommended to upgrade to version 9.8.0, which fixes the issue.  Users unable to upgrade may also safely prevent the issue by using Solr's \"Rule-Based Authentication Plugin\" to restrict access to the configset upload API, so that it can only be accessed by a trusted set of administrators/users.","ecosystems":["Bitnami","Maven"],"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":"Apache Solr: Configset upload on Windows allows arbitrary path write-access","id":"CVE-2024-52012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"path_traversal","year":"2024"},"n_packages":3,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2024-52013"},"packages":[{"ecosystem":"Bitnami","fixed":["9.8.0"],"introduced":["6.6.0"],"last_affected":[],"package":"solr","purl":"pkg:bitnami/solr","source":"BIT-solr-2024-52012"},{"ecosystem":"Maven","fixed":["9.8.0"],"introduced":["6.6"],"last_affected":[],"package":"org.apache.solr:solr-core","purl":null,"source":"GHSA-4p5m-gvpf-f3x5"},{"ecosystem":"Maven","fixed":["9.8.0"],"introduced":["6.6"],"last_affected":[],"package":"org.apache.solr:solr-core","purl":"pkg:maven/org.apache.solr/solr-core","source":"GHSA-4p5m-gvpf-f3x5"}],"prev":{"headline":"launch-editor vulnerable to command injection via the crafted request on Windows","id":"CVE-2024-52011"},"products":["Apache Solr"],"published":"2025-01-27","related":[{"cvss_score":7.5,"headline":"Apache Solr VelocityResponseWriter Plug-In Remote Code Execution","id":"CVE-2019-17558","kev_date_added":"2021-11-03","published":"2019-12-30"},{"cvss_score":7.2,"headline":"Apache Solr DataImportHandler Code Injection","id":"CVE-2019-0193","kev_date_added":"2021-12-10","published":"2019-08-01"},{"cvss_score":9.8,"headline":"Apache Solr: Authentication bypass possible using a fake URL Path ending","id":"CVE-2024-45216","kev_date_added":null,"published":"2024-10-16"},{"cvss_score":9.8,"headline":"Apache Solr information disclosure vulnerability through DataImportHandler","id":"CVE-2021-44548","kev_date_added":null,"published":"2021-12-23"},{"cvss_score":9.8,"headline":"SSRF vulnerability with the Replication handler","id":"CVE-2021-27905","kev_date_added":null,"published":"2021-04-13"},{"cvss_score":9.8,"headline":"Incorrect Authorization in Apache Solr","id":"CVE-2020-13957","kev_date_added":null,"published":"2020-10-13"},{"cvss_score":9.8,"headline":"Unrestricted upload of file with dangerous type in Apache Solr","id":"CVE-2019-12409","kev_date_added":null,"published":"2019-11-18"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-02-06","vendors":["Apache Software Foundation"]},"summary":"Attackers can write arbitrary files to the filesystem on Windows via malicious ZIP uploads in the configset API, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2024-52012/"}