{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-47631 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-47631 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-47631 is a high-severity vulnerability in n/a, published on 14 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-2022-47631 and fix it if it is affected.\n\nWhat it is: CVE-2022-47631 is a high-severity vulnerability in n/a, published on 14 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-47631 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-47631/ (Markdown: https://insights.sbomify.com/CVE-2022-47631/index.md)","id":"CVE-2022-47631","markdown":"https://insights.sbomify.com/CVE-2022-47631/index.md","name":"CVE-2022-47631","record":{"aliases":["GHSA-5q3q-p4gq-p4rp"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Razer Synapse software","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges to administrative level by exploiting a race condition in the Razer Synapse service installation process.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"synapse","vendor":"razer"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-367","name":"Time-of-check Time-of-use (TOCTOU) Race Condition"}],"description":"Razer Synapse through 3.7.1209.121307 allows privilege escalation due to an unsafe installation path and improper privilege management. Attackers can place DLLs into %PROGRAMDATA%\\Razer\\Synapse3\\Service\\bin if they do so before the service is installed and if they deny write access for the SYSTEM user. Although the service will not start if it detects malicious DLLs in this directory, attackers can exploit a race condition and replace a valid DLL (i.e., a copy of a legitimate Razer DLL) with a malicious DLL after the service has already checked the file. As a result, local Windows users can abuse the Razer driver installer to obtain administrative privileges on Windows.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Race condition in n/a","id":"CVE-2022-47631","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2022-47632"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2022-47630"},"products":["n/a"],"published":"2023-09-14","related":[{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-9769","kev_date_added":null,"published":"2017-08-02"},{"cvss_score":8.4,"headline":"Privilege escalation in n/a","id":"CVE-2017-11652","kev_date_added":null,"published":"2017-08-18"},{"cvss_score":7.8,"headline":"Razer Synapse 3 Macro Module Link Following Local Privilege Escalation Vulnerability","id":"CVE-2025-9869","kev_date_added":null,"published":"2025-10-29"},{"cvss_score":7.8,"headline":"Razer Synapse 3 RazerPhilipsHueUninstall Link Following Local Privilege Escalation Vulnerability","id":"CVE-2025-9870","kev_date_added":null,"published":"2025-10-29"},{"cvss_score":7.8,"headline":"Razer Synapse 3 Chroma Connect Link Following Local Privilege Escalation Vulnerability","id":"CVE-2025-9871","kev_date_added":null,"published":"2025-10-29"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-14398","kev_date_added":null,"published":"2017-09-13"}],"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":"Local attackers can escalate privileges to administrative level by exploiting a race condition in the Razer Synapse service installation process.","url":"https://insights.sbomify.com/CVE-2022-47631/"}