# CVE-2019-7651: Security feature bypass in n/a

> Attackers can bypass ACLs in Emsisoft Anti-Malware to impersonate objects or create files, potentially leading to privilege escalation.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-98w4-c4xx-5m56

## What is CVE-2019-7651?

CVE-2019-7651 is a high-severity vulnerability in n/a, published on 8 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EPP.sys in Emsisoft Anti-Malware prior to version 2018.12 allows an attacker to bypass ACLs because Interpreted Device Characteristics lacks FILE_DEVICE_SECURE_OPEN and therefore files and directories "inside" the \\.\EPP device are not properly protected, leading to unintended impersonation or object creation. This vulnerability has been fixed in version 2018.12 and later.

## Which versions are affected by CVE-2019-7651?

It affects 1 product.


Products: Emsisoft Anti-Malware.

## How do I fix CVE-2019-7651?

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

## Is CVE-2019-7651 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1450](https://insights.sbomify.com/CVE-2012-1450/): Security feature bypass in n/a (medium 4.3)
- [CVE-2012-1451](https://insights.sbomify.com/CVE-2012-1451/): Security feature bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7651 and fix it if it is affected.

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

## Sources

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

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