# CVE-2018-5718: Improper restriction of write operations within the bounds of a memory buffer in snscore.sys in SoftControl/SafenSoft SysWatch, SoftControl/


- **Severity:** High 7.1 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5r74-j46m-h77q

## What is CVE-2018-5718?

CVE-2018-5718 is a high-severity vulnerability in n/a, published on 12 Jun 2018. 

### Official description

Improper restriction of write operations within the bounds of a memory buffer in snscore.sys in SoftControl/SafenSoft SysWatch, SoftControl/SafenSoft TPSecure, SoftControl/SafenSoft Enterprise Suite before version 4.4.1 allows local users to cause a denial of service (BSOD) or modify kernel-mode memory via loading of a forged DLL into an user-mode process.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 3 products.


Products: Safensoft Softcontrol Enterprise Suite, Safensoft Softcontrol Syswatch, Safensoft Softcontrol Tpsecure.

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

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

## Is CVE-2018-5718 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-13012](https://insights.sbomify.com/CVE-2018-13012/): Supply chain in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-5718 is a high-severity vulnerability in n/a, published on 12 Jun 2018. 
Exploitation: There is no known exploitation of CVE-2018-5718 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-5718/ (Markdown: https://insights.sbomify.com/CVE-2018-5718/index.md)
```

## Sources

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

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