{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-27812 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-27812 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27812 is a high-severity vulnerability in MSI Center, published on 10 Apr 2025. 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-2025-27812 and fix it if it is affected.\n\nWhat it is: CVE-2025-27812 is a high-severity vulnerability in MSI Center, published on 10 Apr 2025. 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-2025-27812 in the wild and no public exploit code.\n\nAffected product: MSI Center. 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-2025-27812/ (Markdown: https://insights.sbomify.com/CVE-2025-27812/index.md)","id":"CVE-2025-27812","markdown":"https://insights.sbomify.com/CVE-2025-27812/index.md","name":"CVE-2025-27812","record":{"aliases":["GHSA-4h72-4m4g-hr3g"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MSI Center","requires_auth":"none","summary":"A local attacker can exploit a time-of-check time-of-use race condition in MSI Center to escalate privileges.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/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":"MSI Center before 2.0.52.0 allows TOCTOU Local Privilege Escalation.","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 Center","id":"CVE-2025-27812","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in Center","id":"CVE-2025-27813"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2025-27811"},"products":["Center"],"published":"2025-04-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2025-04-10","vendors":["MSI"]},"summary":"A local attacker can exploit a time-of-check time-of-use race condition in MSI Center to escalate privileges.","url":"https://insights.sbomify.com/CVE-2025-27812/"}