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

> Unauthenticated remote attackers can execute arbitrary code or cause denial of service via a stack-based buffer overflow in Xiongmai NVR web servers.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2023
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-pm7h-vr37-wmc9

## What is CVE-2022-45460?

CVE-2022-45460 is a critical memory corruption vulnerability in n/a, published on 28 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple Xiongmai NVR devices, including MBD6304T V4.02.R11.00000117.10001.131900.00000 and NBD6808T-PL V4.02.R11.C7431119.12001.130000.00000, allow an unauthenticated and remote user to exploit a stack-based buffer overflow and crash the web server, resulting in a system reboot. An unauthenticated and remote attacker can execute arbitrary code by sending a crafted HTTP request that triggers the overflow condition via a long URI passed to a sprintf call. NOTE: this is different than CVE-2018-10088, but this may overlap CVE-2017-16725.

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

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

It affects 2 products.


Products: Xiongmaitech Mbd6304t Firmware, Xiongmaitech Nbd6808t-Pl Firmware.

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

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

## Is CVE-2022-45460 being exploited?

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

Public exploit code:

- Proof of Concept for CVE-2022-45460 (github_poc): https://github.com/born0monday/CVE-2022-45460

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45460 is a critical memory corruption vulnerability in n/a, published on 28 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-45460 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-45460/ (Markdown: https://insights.sbomify.com/CVE-2022-45460/index.md)
```

## Sources

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

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