{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19382 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19382 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19382 is a high-severity vulnerability in n/a, published on 3 Dec 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-19382 and fix it if it is affected.\n\nWhat it is: CVE-2019-19382 is a high-severity vulnerability in n/a, published on 3 Dec 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-19382 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-2019-19382/ (Markdown: https://insights.sbomify.com/CVE-2019-19382/index.md)","id":"CVE-2019-19382","markdown":"https://insights.sbomify.com/CVE-2019-19382/index.md","name":"CVE-2019-19382","record":{"aliases":["GHSA-v6xp-4m9g-j2w9"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Antivirus software","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges by replacing executable files in the insecurely permissioned installation directory of Max Secure Anti Virus Plus.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"anti_virus_plus","vendor":"maxpcsecure"}],"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-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Max Secure Anti Virus Plus 19.0.4.020 has Insecure Permissions on the installation directory. Local attackers can replace a .exe or .dll file to achieve privilege escalation.","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":"Privilege escalation in n/a","id":"CVE-2019-19382","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-19383"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-19381"},"products":["n/a"],"published":"2019-12-03","related":[{"cvss_score":5.5,"headline":"Max Secure Anti Virus Plus IoControlCode MaxProc64.sys 0x220019 denial of service","id":"CVE-2023-1492","kev_date_added":null,"published":"2023-03-18"},{"cvss_score":5.5,"headline":"Max Secure Anti Virus Plus IoControlCode MaxProctetor64.sys 0x220019 denial of service","id":"CVE-2023-1493","kev_date_added":null,"published":"2023-03-18"},{"cvss_score":4.4,"headline":"Max Secure Anti Virus Plus IoControlCode SDActMon.sys 0x220020 access control","id":"CVE-2023-1490","kev_date_added":null,"published":"2023-03-18"},{"cvss_score":4.4,"headline":"Max Secure Anti Virus Plus IoControlCode MaxCryptMon.sys 0x220020 access control","id":"CVE-2023-1491","kev_date_added":null,"published":"2023-03-18"}],"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-05","vendors":["n/a"]},"summary":"Local attackers can escalate privileges by replacing executable files in the insecurely permissioned installation directory of Max Secure Anti Virus Plus.","url":"https://insights.sbomify.com/CVE-2019-19382/"}