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

> A buffer overflow in the Tenda AC9 router's httpd service allows attackers to execute arbitrary code via the form_fast_setting_wifi_set endpoint.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 19 Aug 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-p74g-vq49-qc26

## What is CVE-2022-36233?

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

### Official description

Tenda AC9 V15.03.2.13 is vulnerable to Buffer Overflow via httpd, form_fast_setting_wifi_set. httpd.

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

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

It affects 1 product.


Products: Tendacn Ac9 Firmware.

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

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

## Is CVE-2022-36233 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-40942](https://insights.sbomify.com/CVE-2023-40942/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-7561](https://insights.sbomify.com/CVE-2018-7561/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-31624](https://insights.sbomify.com/CVE-2021-31624/): Memory corruption in n/a (high 8.8)
- [CVE-2021-31627](https://insights.sbomify.com/CVE-2021-31627/): Memory corruption in n/a (high 8.8)
- [CVE-2020-20746](https://insights.sbomify.com/CVE-2020-20746/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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