{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10649 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10649 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10649 is a high-severity code injection vulnerability in n/a, published on 25 Mar 2020. 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-2020-10649 and fix it if it is affected.\n\nWhat it is: CVE-2020-10649 is a high-severity code injection vulnerability in n/a, published on 25 Mar 2020. 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-2020-10649 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-2020-10649/ (Markdown: https://insights.sbomify.com/CVE-2020-10649/index.md)","id":"CVE-2020-10649","markdown":"https://insights.sbomify.com/CVE-2020-10649/index.md","name":"CVE-2020-10649","record":{"aliases":["GHSA-xqx8-64m4-pqcg"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"ASUS Device Activation","requires_auth":"low_privilege","summary":"An attacker can execute unsigned code by placing a malicious application at a specific path, affecting ASUS Device Activation on Windows.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"device_activation","vendor":"asus"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"DevActSvc.exe in ASUS Device Activation before 1.0.7.0 for Windows 10 notebooks and PCs could lead to unsigned code execution with no additional restrictions when a user puts an application at a particular path with a particular file name.","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":"Code injection in n/a","id":"CVE-2020-10649","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"jackson-databind vulnerable to unsafe deserialization","id":"CVE-2020-10650"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2020-10648"},"products":["n/a"],"published":"2020-03-25","related":[],"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":"An attacker can execute unsigned code by placing a malicious application at a specific path, affecting ASUS Device Activation on Windows.","url":"https://insights.sbomify.com/CVE-2020-10649/"}