# CVE-2023-7222: Totolink X2000R HTTP POST Request boa formTmultiAP buffer overflow

> Remote attackers can trigger a buffer overflow in the Totolink X2000R router via a crafted HTTP POST request, potentially leading to code execution or service disruption.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jan 2024
- **Updated:** 14 Nov 2024
- **Also known as:** GHSA-jjvf-rww2-493v

## What is CVE-2023-7222?

CVE-2023-7222 is a high-severity memory corruption vulnerability in Totolink X2000R, published on 9 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was found in Totolink X2000R 1.0.0-B20221212.1452. It has been declared as critical. This vulnerability affects the function formTmultiAP of the file /bin/boa of the component HTTP POST Request Handler. The manipulation of the argument submit-url leads to buffer overflow. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-249856. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-787 (Out-of-bounds Write), CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Totolink X2000r Firmware.

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

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

## Is CVE-2023-7222 being exploited?

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

## Other vulnerabilities in Totolink X2000R

- [CVE-2024-22529](https://insights.sbomify.com/CVE-2024-22529/): Command injection in n/a (critical 9.8)
- [CVE-2023-51133](https://insights.sbomify.com/CVE-2023-51133/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-51135](https://insights.sbomify.com/CVE-2023-51135/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-51136](https://insights.sbomify.com/CVE-2023-51136/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-46545](https://insights.sbomify.com/CVE-2023-46545/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7222 and fix it if it is affected.

What it is: CVE-2023-7222 is a high-severity memory corruption vulnerability in Totolink X2000R, published on 9 Jan 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-7222 in the wild and no public exploit code.

Affected product: Totolink X2000R. 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-7222/ (Markdown: https://insights.sbomify.com/CVE-2023-7222/index.md)
```

## Sources

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

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