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

> Attackers can cause a Denial of Service on Xiongmai DVR devices by sending a crafted RTSP request due to a buffer overflow.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-wg24-cp5h-mg67

## What is CVE-2022-26259?

CVE-2022-26259 is a high-severity memory corruption vulnerability in n/a, published on 28 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A buffer over flow in Xiongmai DVR devices NBD80X16S-KL, NBD80X09S-KL, NBD80X08S-KL, NBD80X09RA-KL, AHB80X04R-MH, AHB80X04R-MH-V2, AHB80X04-R-MH-V3, AHB80N16T-GS, AHB80N32F4-LME, and NBD90S0VT-QW allows attackers to cause a Denial of Service (DoS) via a crafted RSTP request.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 10 products.


Products: Xiongmaitech Ahb80n16t-Gs Firmware, Xiongmaitech Ahb80n32f4-Lme Firmware, Xiongmaitech Ahb80x04-R-Mh-V3 Firmware, Xiongmaitech Ahb80x04r-Mh-V2 Firmware, Xiongmaitech Ahb80x04r-Mh Firmware, Xiongmaitech Nbd80x08s-Kl Firmware, Xiongmaitech Nbd80x09ra-Kl Firmware, Xiongmaitech Nbd80x09s-Kl Firmware, Xiongmaitech Nbd80x16s-Kl Firmware, Xiongmaitech Nbd90s0vt-Qw Firmware.

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

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

## Is CVE-2022-26259 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-26259 is a high-severity memory corruption vulnerability in n/a, published on 28 Mar 2022. 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-2022-26259 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-2022-26259/ (Markdown: https://insights.sbomify.com/CVE-2022-26259/index.md)
```

## Sources

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

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