{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-10716 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-10716 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-10716 is a medium-severity vulnerability in n/a, published on 3 May 2018. 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-2018-10716 and fix it if it is affected.\n\nWhat it is: CVE-2018-10716 is a medium-severity vulnerability in n/a, published on 3 May 2018. 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-2018-10716 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-2018-10716/ (Markdown: https://insights.sbomify.com/CVE-2018-10716/index.md)","id":"CVE-2018-10716","markdown":"https://insights.sbomify.com/CVE-2018-10716/index.md","name":"CVE-2018-10716","record":{"aliases":["GHSA-hcpq-q5r9-f88g"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["security_bypass","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Security Guard software","requires_auth":"low_privilege","summary":"Local attackers can bypass process protections in Shanghai 2345 Security Guard to terminate protected processes via improper WM_CLOSE handling.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"2345_security_guard","vendor":"2345_security_guard_project"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[],"description":"An issue was discovered in Shanghai 2345 Security Guard 3.7.0. 2345MPCSafe.exe, 2345SafeTray.exe, and 2345Speedup.exe allow local users to bypass intended process protections, and consequently terminate processes, because WM_CLOSE is not properly considered.","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":"Security feature bypass in n/a","id":"CVE-2018-10716","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-10717"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-10713"},"products":["n/a"],"published":"2018-05-03","related":[{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2018-10952","kev_date_added":null,"published":"2018-05-10"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2018-10953","kev_date_added":null,"published":"2018-05-10"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2018-10954","kev_date_added":null,"published":"2018-05-10"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2018-10955","kev_date_added":null,"published":"2018-05-10"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2018-10830","kev_date_added":null,"published":"2018-05-09"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2018-10809","kev_date_added":null,"published":"2018-05-08"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2018-10796","kev_date_added":null,"published":"2018-05-07"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["n/a"]},"summary":"Local attackers can bypass process protections in Shanghai 2345 Security Guard to terminate protected processes via improper WM_CLOSE handling.","url":"https://insights.sbomify.com/CVE-2018-10716/"}