# CVE-2022-40784: Memory corruption in n/a

> Unlimited strcpy on user input causes stack buffer overflow in mIPC camera firmware, potentially allowing remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2022
- **Updated:** 22 May 2025
- **Also known as:** GHSA-7fvx-cw5x-7cm3

## What is CVE-2022-40784?

CVE-2022-40784 is a high-severity memory corruption vulnerability in n/a, published on 26 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unlimited strcpy on user input when setting a locale file leads to stack buffer overflow in mIPC camera firmware 5.3.1.2003161406.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2022-40784?

It affects 1 product.


Products: Mipcm Mipc Camera Firmware.

## How do I fix CVE-2022-40784?

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

## Is CVE-2022-40784 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40784 exists.

## Other vulnerabilities in n/a

- [CVE-2022-40785](https://insights.sbomify.com/CVE-2022-40785/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40784 and fix it if it is affected.

What it is: CVE-2022-40784 is a high-severity memory corruption vulnerability in n/a, published on 26 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40784 exists.

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-2022-40784/ (Markdown: https://insights.sbomify.com/CVE-2022-40784/index.md)
```

## Sources

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

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