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

> A buffer overflow in the Tenda TX9 Pro router's httpd service allows attackers to execute arbitrary code or cause a denial of service.

- **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 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-8mg5-92fc-9xrp

## What is CVE-2022-38510?

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

### Official description

Tenda_TX9pro V22.03.02.10 was discovered to contain a buffer overflow via the component httpd/SetNetControlList.

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

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

It affects 1 product.


Products: Tenda Tx9 Pro Firmware.

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

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

## Is CVE-2022-38510 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-29591](https://insights.sbomify.com/CVE-2022-29591/): Memory corruption in n/a (critical 9.8)
- [CVE-2022-29592](https://insights.sbomify.com/CVE-2022-29592/): Command injection in n/a (critical 9.8)
- [CVE-2024-4111](https://insights.sbomify.com/CVE-2024-4111/): Tenda TX9 SetLEDCfg sub_42BD7C stack-based overflow (high 8.8)
- [CVE-2024-4112](https://insights.sbomify.com/CVE-2024-4112/): Tenda TX9 SetVirtualServerCfg sub_42CB94 stack-based overflow (high 8.8)
- [CVE-2024-4113](https://insights.sbomify.com/CVE-2024-4113/): Tenda TX9 SetSysTimeCfg sub_42D4DC stack-based overflow (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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