{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-3610 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-3610 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-3610 is a medium-severity vulnerability in McAfee, LLC True Key (TK), published on 13 Feb 2019. 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-2019-3610 and fix it if it is affected.\n\nWhat it is: CVE-2019-3610 is a medium-severity vulnerability in McAfee, LLC True Key (TK), published on 13 Feb 2019. 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-2019-3610 in the wild and no public exploit code.\n\nAffected product: McAfee, LLC True Key (TK). 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-2019-3610/ (Markdown: https://insights.sbomify.com/CVE-2019-3610/index.md)","id":"CVE-2019-3610","markdown":"https://insights.sbomify.com/CVE-2019-3610/index.md","name":"CVE-2019-3610","record":{"aliases":["GHSA-x9hw-3v72-w69p"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"McAfee True Key extension","requires_auth":"low_privilege","summary":"Local attackers can expose confidential data from the McAfee True Key browser extension via specially crafted malware.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"trellix","cpe":[{"product":"true_key","vendor":"mcafee"}],"cvss":{"score":5.6,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Data Leakage Attacks vulnerability in Microsoft Windows client in McAfee True Key (TK) 3.1.9211.0 and earlier allows local users to expose confidential data via specially crafted malware.","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":"True Key Browser Extension 3.1.9219.0 update fixes Sensitive Data Exposure vulnerability","id":"CVE-2019-3610","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure vulnerability in McAfee TIE Server and DXL Platform","id":"CVE-2019-3612"},"packages":[],"prev":{"headline":"Data leakage when in an MDR pair by McAfee Network Security Manager 9.x","id":"CVE-2019-3606"},"products":["True Key (TK)"],"published":"2019-02-13","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.5,"headline":"TS102801 True Key DLL Side-Loading vulnerability","id":"CVE-2018-6661","kev_date_added":null,"published":"2018-04-02"},{"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"}],"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, LLC"]},"summary":"Local attackers can expose confidential data from the McAfee True Key browser extension via specially crafted malware.","url":"https://insights.sbomify.com/CVE-2019-3610/"}