{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-45975 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-45975 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-45975 is a high-severity vulnerability in n/a, published on 26 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-45975 and fix it if it is affected.\n\nWhat it is: CVE-2021-45975 is a high-severity vulnerability in n/a, published on 26 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-45975 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-2021-45975/ (Markdown: https://insights.sbomify.com/CVE-2021-45975/index.md)","id":"CVE-2021-45975","markdown":"https://insights.sbomify.com/CVE-2021-45975/index.md","name":"CVE-2021-45975","record":{"aliases":["GHSA-wj79-qqhx-jqhr"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Acer Care Center","requires_auth":"none","summary":"Local attackers can execute arbitrary code with administrator privileges via DLL hijacking in Acer Care Center due to insecure library loading.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"care_center","vendor":"acer"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"In ListCheck.exe in Acer Care Center 4.x before 4.00.3038, a vulnerability in the loading mechanism of Windows DLLs could allow a local attacker to perform a DLL hijacking attack. This vulnerability is due to incorrect handling of directory search paths at run time. An attacker could exploit this vulnerability by placing a malicious DLL file on the targeted system. This file will execute when the vulnerable application launches. A successful exploit could allow the attacker to execute arbitrary code on the targeted system with local administrator privileges.","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":"Other in n/a","id":"CVE-2021-45975","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Misconfiguration in n/a","id":"CVE-2021-45977"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2021-45972"},"products":["n/a"],"published":"2022-01-26","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2022-24285","kev_date_added":null,"published":"2022-03-08"},{"cvss_score":6.8,"headline":"Acer Care Center creates a Named Pipe with a weak Security Descriptor","id":"CVE-2026-9490","kev_date_added":null,"published":"2026-05-25"}],"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-04","vendors":["n/a"]},"summary":"Local attackers can execute arbitrary code with administrator privileges via DLL hijacking in Acer Care Center due to insecure library loading.","url":"https://insights.sbomify.com/CVE-2021-45975/"}