# CVE-2023-1646: IObit Malware Fighter IOCTL IMFCameraProtect.sys 0x8018E004 stack-based overflow

> A local attacker can exploit a stack-based buffer overflow in the IMFCameraProtect.sys driver to execute arbitrary code with elevated privileges.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 26 Mar 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9rc9-gp35-8v5g

## What is CVE-2023-1646?

CVE-2023-1646 is a medium-severity memory corruption vulnerability in IObit Malware Fighter, published on 26 Mar 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in IObit Malware Fighter 9.4.0.776. It has been declared as critical. This vulnerability affects the function 0x8018E000/0x8018E004 in the library IMFCameraProtect.sys of the component IOCTL Handler. The manipulation leads to stack-based buffer overflow. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. VDB-224026 is the identifier assigned to this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2023-1646?

It affects 1 product.


Products: Iobit Malware Fighter.

## How do I fix CVE-2023-1646?

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

## Is CVE-2023-1646 being exploited?

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

## Other vulnerabilities in IObit Malware Fighter

- [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-2023-1646 and fix it if it is affected.

What it is: CVE-2023-1646 is a medium-severity memory corruption vulnerability in IObit Malware Fighter, published on 26 Mar 2023. 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-2023-1646 in the wild and no public exploit code.

Affected product: IObit Malware Fighter. 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-2023-1646/ (Markdown: https://insights.sbomify.com/CVE-2023-1646/index.md)
```

## Sources

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

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