# CVE-2019-6494: Missing authorization in n/a

> A low-privileged user can delete arbitrary files via a specific IOCTL call in IObit Malware Fighter, bypassing standard access controls.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rj7p-8gjh-5gqf

## What is CVE-2019-6494?

CVE-2019-6494 is a medium-severity missing authorization vulnerability in n/a, published on 30 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IMFForceDelete.sys in IObit Malware Fighter 6.2 allows a low privileged user to send IOCTL 0x8016E000 along with a user defined string to a file; that file will be promptly deleted regardless of access controls.

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

It affects 1 product.


Products: Iobit Malware Fighter.

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

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

## Is CVE-2019-6494 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-20059](https://insights.sbomify.com/CVE-2016-20059/): IObit Malware Fighter 4.3.1 Unquoted Service Path Privilege Escalation (high 8.5)
- [CVE-2020-23864](https://insights.sbomify.com/CVE-2020-23864/): Privilege escalation in n/a (high 7.8)
- [CVE-2018-19084](https://insights.sbomify.com/CVE-2018-19084/): Memory corruption in n/a (high 7.8)
- [CVE-2018-19085](https://insights.sbomify.com/CVE-2018-19085/): Memory corruption in n/a (high 7.8)
- [CVE-2018-19086](https://insights.sbomify.com/CVE-2018-19086/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6494 is a medium-severity missing authorization vulnerability in n/a, published on 30 Apr 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-6494 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-6494/ (Markdown: https://insights.sbomify.com/CVE-2019-6494/index.md)
```

## Sources

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

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