# CVE-2018-10425: Security feature bypass in n/a

> Local attackers can bypass process protections in Shanghai 2345 Security Guard to terminate protected processes due to improper handling of SetParent.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5rh8-99j5-q6fm

## What is CVE-2018-10425?

CVE-2018-10425 is a high-severity vulnerability in n/a, published on 26 Apr 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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 SetParent is not properly considered.

## Which versions are affected by CVE-2018-10425?

It affects 1 product.


Products: Hz-Soft Security Guard.

## How do I fix CVE-2018-10425?

No fix has been published for CVE-2018-10425 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-10425 being exploited?

There is no known exploitation of CVE-2018-10425 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10425 and fix it if it is affected.

What it is: CVE-2018-10425 is a high-severity vulnerability in n/a, published on 26 Apr 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-10425 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-10425/ (Markdown: https://insights.sbomify.com/CVE-2018-10425/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-10425
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-10425
- OSV: https://osv.dev/vulnerability/CVE-2018-10425

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-10425/
Summaries are generated and may contain mistakes; the official description above is the record.