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

> Local attackers can bypass code-signing protections in SysWatch to install and execute unauthorized programs by modifying system configuration.

- **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:** 29 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qmfq-w4vr-f499

## What is CVE-2018-13013?

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

### Official description

Improper check of unusual conditions when launching msiexec.exe in safensec.com (SysWatch service) in SAFE'N'SEC SoftControl/SafenSoft SysWatch, SoftControl/SafenSoft TPSecure, and SoftControl/SafenSoft Enterprise Suite before 4.4.9 allows the local attacker to bypass a code-signing protection mechanism and install/execute an unauthorized program by modifying the system configuration and installing a forged MSI file. (The intended behavior is that the component SysWatch does not allow installation of MSI files unless they are signed by a limited list of certificates.)

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

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

It affects 3 products.


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

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

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

## Is CVE-2018-13013 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-13014](https://insights.sbomify.com/CVE-2018-13014/): Hardcoded credentials in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-13013 is a high-severity vulnerability in n/a, published on 29 Jun 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-13013 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-13013/ (Markdown: https://insights.sbomify.com/CVE-2018-13013/index.md)
```

## Sources

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

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