# CVE-2018-6593: Privilege escalation in n/a

> A local attacker can exploit improper access control in the MalwareFox driver to elevate privileges via a specific IOCTL call.

- **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:** 3 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jrgv-wc94-68jw

## What is CVE-2018-6593?

CVE-2018-6593 is a high-severity vulnerability in n/a, published on 3 Feb 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 MalwareFox AntiMalware 2.74.0.150. Improper access control in zam32.sys and zam64.sys allows a non-privileged process to register itself with the driver by connecting to the filter communication port and then using IOCTL 0x8000204C to \\.\ZemanaAntiMalware to elevate privileges.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Malwarefox Antimalware.

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

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

## Is CVE-2018-6593 being exploited?

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

Public exploit code:

- MalwareFox AntiMalware 2.74.0.150 - Local Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-31727](https://insights.sbomify.com/CVE-2021-31727/): Missing authorization in n/a (high 7.8)
- [CVE-2021-31728](https://insights.sbomify.com/CVE-2021-31728/): Privilege escalation in n/a (high 7.8)
- [CVE-2018-6606](https://insights.sbomify.com/CVE-2018-6606/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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