{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-3636 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-3636 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-3636 is a high-severity vulnerability in McAfee, LCC McAfee Total Protection, published on 28 Oct 2019. 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-2019-3636 and fix it if it is affected.\n\nWhat it is: CVE-2019-3636 is a high-severity vulnerability in McAfee, LCC McAfee Total Protection, published on 28 Oct 2019. 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-2019-3636 in the wild and no public exploit code.\n\nAffected product: McAfee, LCC McAfee Total Protection. 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-3636/ (Markdown: https://insights.sbomify.com/CVE-2019-3636/index.md)","id":"CVE-2019-3636","markdown":"https://insights.sbomify.com/CVE-2019-3636/index.md","name":"CVE-2019-3636","record":{"aliases":["GHSA-fcqr-w4fr-6f6x"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"McAfee Total Protection","requires_auth":"low_privilege","summary":"Attackers can read antivirus exclusion lists from the registry and replace excluded files with malware, bypassing detection in McAfee Total Protection.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"trellix","cpe":[{"product":"total_protection","vendor":"mcafee"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"A File Masquerade vulnerability in McAfee Total Protection (MTP) version 16.0.R21 and earlier in Windows client allowed an attacker to read the plaintext list of AV-Scan exclusion files from the Windows registry, and to possibly replace excluded files with potential malware without being detected.","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":"File masquerade attack vulnerability in McAfee Total Protection","id":"CVE-2019-3636","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege Escalation vulnerability in FRP 5.x earlier than 5.1.0.209","id":"CVE-2019-3637"},"packages":[],"prev":{"headline":"MWG Proxy: Cross-Frame Scripting vulnerability","id":"CVE-2019-3635"},"products":["McAfee Total Protection"],"published":"2019-10-28","related":[{"cvss_score":8.2,"headline":"McAfee Total Protection (MTP) Improper Privilege Management","id":"CVE-2021-23874","kev_date_added":"2021-11-03","published":"2021-02-10"},{"cvss_score":7.8,"headline":"Security feature bypass in n/a","id":"CVE-2023-24579","kev_date_added":null,"published":"2023-03-13"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2022-43751","kev_date_added":null,"published":"2022-11-22"},{"cvss_score":7.8,"headline":"Privilege Escalation vulnerability in McAfee Total Protection (MTP)","id":"CVE-2021-23872","kev_date_added":null,"published":"2021-05-12"},{"cvss_score":7.8,"headline":"Privilege Escalation vulnerability in McAfee Total Protection (MTP)","id":"CVE-2021-23891","kev_date_added":null,"published":"2021-05-12"},{"cvss_score":7.8,"headline":"McAfee Total Protection (MTP) privilege escalation vulnerability","id":"CVE-2021-23873","kev_date_added":null,"published":"2021-02-10"},{"cvss_score":7.8,"headline":"McAfee Total Protection (MTP) Bypass Remote Procedure call vulnerability","id":"CVE-2021-23876","kev_date_added":null,"published":"2021-02-10"}],"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-17","vendors":["McAfee, LCC"]},"summary":"Attackers can read antivirus exclusion lists from the registry and replace excluded files with malware, bypassing detection in McAfee Total Protection.","url":"https://insights.sbomify.com/CVE-2019-3636/"}