{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-37907 exists.","fix":"No fix has been published for CVE-2023-37907 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-37907 is a high-severity vulnerability in cryptomator, published on 25 Jul 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-37907 and fix it if it is affected.\n\nWhat it is: CVE-2023-37907 is a high-severity vulnerability in cryptomator, published on 25 Jul 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-37907 exists.\n\nAffected product: cryptomator. 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-2023-37907/ (Markdown: https://insights.sbomify.com/CVE-2023-37907/index.md)","id":"CVE-2023-37907","markdown":"https://insights.sbomify.com/CVE-2023-37907/index.md","name":"CVE-2023-37907","record":{"aliases":["GHSA-9c9p-c3mg-hpjq"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Cryptomator desktop app","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges via the MSI repair function spawning administrative commands in Cryptomator.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cryptomator","vendor":"cryptomator"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"Cryptomator is data encryption software for users who store their files in the cloud. Prior to version 1.9.2, the MSI installer provided on the homepage allows local privilege escalation (LPE) for low privileged users, if already installed. The problem occurs as the repair function of the MSI spawns two administrative CMDs. A simple LPE is possible via a breakout. Version 1.9.2 fixes this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cryptomator's MSI installer allows local privilege escalation","id":"CVE-2023-37907","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2023"},"n_packages":0,"n_references":3,"next":{"headline":"org.xwiki.rendering:xwiki-rendering-xml Improper Neutralization of Invalid Characters in Identifiers in Web Pages vulnerability","id":"CVE-2023-37908"},"packages":[],"prev":{"headline":"Discourse vulnerable to DoS via post edit reason","id":"CVE-2023-37906"},"products":["cryptomator"],"published":"2023-07-25","related":[{"cvss_score":8.7,"headline":"Cryptomator: Hub unlocking accepts plaintext HTTP and unvalidated endpoint schemes","id":"CVE-2026-32309","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.8,"headline":"Code injection in n/a","id":"CVE-2022-25366","kev_date_added":null,"published":"2022-02-19"},{"cvss_score":7.6,"headline":"Cryptomator: Tampered vault configuration allows MITM attack on Hub API","id":"CVE-2026-32303","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.6,"headline":"Cryptomator for Android: Tampered vault configuration allows MITM attack on Hub API","id":"CVE-2026-32317","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.6,"headline":"Cryptomator for IOS: Tampered vault configuration allows MITM attack on Hub API","id":"CVE-2026-32318","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":5.5,"headline":"Cryptomator vulnerable to Local Elevation of Privileges","id":"CVE-2023-39520","kev_date_added":null,"published":"2023-08-07"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-03","vendors":["cryptomator"]},"summary":"Local attackers can escalate privileges via the MSI repair function spawning administrative commands in Cryptomator.","url":"https://insights.sbomify.com/CVE-2023-37907/"}