{"answers":{"affected":"1 open source package ship an affected version, including miniconda. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-35845 exists.","fix":"No fix has been published for CVE-2023-35845 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-35845 is a medium-severity vulnerability in n/a, published on 11 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-35845 and fix it if it is affected.\n\nWhat it is: CVE-2023-35845 is a medium-severity vulnerability in n/a, published on 11 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-35845 exists.\n\nAffected packages and fixed versions:\n- miniconda (Bitnami): affected from 2023.03-1.0 up to 2023.03-1.0; no fix listed\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-2023-35845/ (Markdown: https://insights.sbomify.com/CVE-2023-35845/index.md)","id":"CVE-2023-35845","markdown":"https://insights.sbomify.com/CVE-2023-35845/index.md","name":"CVE-2023-35845","record":{"aliases":["BIT-miniconda-2023-35845","GHSA-hhfv-2xc3-52h6"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Anaconda distribution","requires_auth":"low_privilege","summary":"Local attackers can bypass TLS certificate validation by modifying world-writable files in Anaconda or Miniconda installations.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"anaconda3","vendor":"anaconda"}],"cvss":{"score":4.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Anaconda 3 2023.03-1-Linux allows local users to disrupt TLS certificate validation by modifying the cacert.pem file used by the installed pip program. This occurs because many files are installed as world-writable on Linux, ignoring umask, even when these files are installed as root. Miniconda is also affected.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Security feature bypass in n/a","id":"CVE-2023-35845","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":1,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2023-35846"},"packages":[{"ecosystem":"Bitnami","fixed":[],"introduced":["2023.03-1.0"],"last_affected":["2023.03-1.0"],"package":"miniconda","purl":"pkg:bitnami/miniconda","source":"BIT-miniconda-2023-35845"}],"prev":{"headline":"Path traversal in n/a","id":"CVE-2023-35844"},"products":["n/a"],"published":"2023-09-11","related":[{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2021-42969","kev_date_added":null,"published":"2022-05-13"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2024-46060","kev_date_added":null,"published":"2025-12-17"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2022-26526","kev_date_added":null,"published":"2022-03-17"}],"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":"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-26","vendors":["n/a"]},"summary":"Local attackers can bypass TLS certificate validation by modifying world-writable files in Anaconda or Miniconda installations.","url":"https://insights.sbomify.com/CVE-2023-35845/"}