# CVE-2018-13012: Supply chain in n/a

> Remote attackers can execute unauthorized code by substituting a forged update server due to improper integrity checks in update mechanisms.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p3mh-hp36-p892

## What is CVE-2018-13012?

CVE-2018-13012 is a high-severity vulnerability in n/a, published on 29 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Download of code with improper integrity check in snsupd.exe and upd.exe in SAFE'N'SEC SoftControl/SafenSoft SysWatch, SoftControl/SafenSoft TPSecure, and SoftControl/SafenSoft Enterprise Suite before 4.4.12 allows the remote attacker to execute unauthorized code by substituting a forged update server.

Weakness: CWE-494 (Download of Code Without Integrity Check)

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

It affects 3 products.


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

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

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

## Is CVE-2018-13012 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-5718](https://insights.sbomify.com/CVE-2018-5718/): Improper restriction of write operations within the bounds of a memory buffer in snscore.sys in SoftControl/SafenSoft SysWatch, SoftControl/ (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-13012 is a high-severity vulnerability in n/a, published on 29 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-13012 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-13012/ (Markdown: https://insights.sbomify.com/CVE-2018-13012/index.md)
```

## Sources

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

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