{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15722 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-15722 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-15722 is a high-severity vulnerability in 360 Total Security, published on 21 Jul 2020. 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-2020-15722 and fix it if it is affected.\n\nWhat it is: CVE-2020-15722 is a high-severity vulnerability in 360 Total Security, published on 21 Jul 2020. 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-2020-15722 in the wild and no public exploit code.\n\nAffected product: 360 Total Security. 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-15722/ (Markdown: https://insights.sbomify.com/CVE-2020-15722/index.md)","id":"CVE-2020-15722","markdown":"https://insights.sbomify.com/CVE-2020-15722/index.md","name":"CVE-2020-15722","record":{"aliases":["GHSA-wqwc-q68g-5fjg"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"360 Total Security","requires_auth":"none","summary":"Local attackers can exploit DLL hijacking in 360 Total Security to execute arbitrary code with elevated privileges.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"360ST","cpe":[{"product":"360_total_security","vendor":"360totalsecurity"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"description":"In version 12.1.0.1004 and below of 360 Total Security,when TPI calls the browser process, there exists a local privilege escalation vulnerability. An attacker who could exploit DLL hijacking could execute arbitrary code on the Local system.","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 360 Total Security","id":"CVE-2020-15722","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in 360 Total Security","id":"CVE-2020-15723"},"packages":[],"prev":{"headline":"Cross-site Scripting in RosarioSIS","id":"CVE-2020-15721"},"products":["360 Total Security"],"published":"2020-07-21","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2024-22014","kev_date_added":null,"published":"2024-04-15"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2021-33973","kev_date_added":null,"published":"2023-04-19"},{"cvss_score":7.8,"headline":"Privilege escalation in 360 Total Security","id":"CVE-2020-15723","kev_date_added":null,"published":"2020-07-21"},{"cvss_score":7.8,"headline":"Privilege escalation in 360 Total Security","id":"CVE-2020-15724","kev_date_added":null,"published":"2020-07-21"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-12653","kev_date_added":null,"published":"2017-08-07"},{"cvss_score":6.3,"headline":"Code injection in n/a","id":"CVE-2018-18603","kev_date_added":null,"published":"2018-10-23"}],"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":"Local attackers can exploit DLL hijacking in 360 Total Security to execute arbitrary code with elevated privileges.","url":"https://insights.sbomify.com/CVE-2020-15722/"}