# CVE-2024-4113: Tenda TX9 SetSysTimeCfg sub_42D4DC stack-based overflow

> Remote attackers can trigger a stack-based buffer overflow in the Tenda TX9 router's time configuration interface, potentially leading to arbitrary code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-f755-p72c-mhgq

## What is CVE-2024-4113?

CVE-2024-4113 is a high-severity memory corruption vulnerability in Tenda TX9, published on 24 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical was found in Tenda TX9 22.03.02.10. This vulnerability affects the function sub_42D4DC of the file /goform/SetSysTimeCfg. The manipulation of the argument time leads to stack-based 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-261856. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2024-4113?

It affects 1 product.


Products: Tenda Tx9 Pro Firmware.

## How do I fix CVE-2024-4113?

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

## Is CVE-2024-4113 being exploited?

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

## Other vulnerabilities in Tenda TX9

- [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-4114](https://insights.sbomify.com/CVE-2024-4114/): Tenda TX9 PowerSaveSet sub_42C014 stack-based overflow (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4113 and fix it if it is affected.

What it is: CVE-2024-4113 is a high-severity memory corruption vulnerability in Tenda TX9, published on 24 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4113 exists.

Affected product: Tenda TX9. 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-2024-4113/ (Markdown: https://insights.sbomify.com/CVE-2024-4113/index.md)
```

## Sources

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

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