{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-6661 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-6661 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-6661 is a high-severity vulnerability in McAfee True Key, published on 2 Apr 2018. 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-2018-6661 and fix it if it is affected.\n\nWhat it is: CVE-2018-6661 is a high-severity vulnerability in McAfee True Key, published on 2 Apr 2018. 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-2018-6661 in the wild and no public exploit code.\n\nAffected product: McAfee True Key. 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-2018-6661/ (Markdown: https://insights.sbomify.com/CVE-2018-6661/index.md)","id":"CVE-2018-6661","markdown":"https://insights.sbomify.com/CVE-2018-6661/index.md","name":"CVE-2018-6661","record":{"aliases":["GHSA-rr9p-522h-f7f2"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"McAfee True Key","requires_auth":"low_privilege","summary":"Local attackers can gain elevated privileges by exploiting a DLL side-loading vulnerability in McAfee True Key due to missing signature verification.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"trellix","cpe":[{"product":"true_key","vendor":"mcafee"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"DLL Side-Loading vulnerability in Microsoft Windows Client in McAfee True Key before 4.20.110 allows local users to gain privilege elevation via not verifying a particular DLL file signature.","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":"TS102801 True Key DLL Side-Loading vulnerability","id":"CVE-2018-6661","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"SB10232 - McAfee Management of Native Encryption (MNE) - Privilege Escalation vulnerability","id":"CVE-2018-6662"},"packages":[],"prev":{"headline":"SB10228 ePO Directory Traversal vulnerability","id":"CVE-2018-6660"},"products":["True Key"],"published":"2018-04-02","related":[{"cvss_score":7.8,"headline":"True Key (TK) Windows Client - Authentication Abuse vulnerability","id":"CVE-2018-6756","kev_date_added":null,"published":"2018-12-06"},{"cvss_score":7.5,"headline":"True Key (TK) Windows Client - Privilege Escalation vulnerability","id":"CVE-2018-6757","kev_date_added":null,"published":"2018-12-06"},{"cvss_score":7.5,"headline":"True Key (TK) - DLL Search Order Hijacking vulnerability","id":"CVE-2018-6700","kev_date_added":null,"published":"2018-09-24"},{"cvss_score":7.2,"headline":"True Key (TK) Windows Client - Weak Directory Permission Vulnerability","id":"CVE-2018-6755","kev_date_added":null,"published":"2018-12-06"},{"cvss_score":5.9,"headline":"True Key (TK) - Cross Site Scripting Exposure","id":"CVE-2018-6682","kev_date_added":null,"published":"2018-09-24"},{"cvss_score":5.6,"headline":"True Key Browser Extension 3.1.9219.0 update fixes Sensitive Data Exposure vulnerability","id":"CVE-2019-3610","kev_date_added":null,"published":"2019-02-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-09-16","vendors":["McAfee"]},"summary":"Local attackers can gain elevated privileges by exploiting a DLL side-loading vulnerability in McAfee True Key due to missing signature verification.","url":"https://insights.sbomify.com/CVE-2018-6661/"}