# CVE-2024-10523: Information Disclosure Vulnerability in TP-Link IoT Smart Hub

> Attackers with physical access can extract Wi-Fi credentials from the device firmware due to plain text storage.

- **Severity:** Medium 4.4 (`CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2024
- **Updated:** 4 Nov 2024
- **Also known as:** GHSA-rhh2-f22c-xh7f

## What is CVE-2024-10523?

CVE-2024-10523 is a medium-severity vulnerability in TP-Link Tapo H100 IoT Smart Hub, published on 4 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This vulnerability exists in TP-Link IoT Smart Hub due to storage of Wi-Fi credentials in plain text within the device firmware. An attacker with physical access could exploit this by extracting the firmware and analyzing the binary data to obtain the Wi-Fi credentials stored on the vulnerable device.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Tp-Link Tapo H100 Firmware.

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

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

## Is CVE-2024-10523 being exploited?

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

## Other vulnerabilities in TP-Link Tapo H100 IoT Smart Hub

- [CVE-2025-15557](https://insights.sbomify.com/CVE-2025-15557/): Improper Certificate Validation in TP-Link Tapo H100 and P100 Allows Man-in-the-Middle Attack (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10523 is a medium-severity vulnerability in TP-Link Tapo H100 IoT Smart Hub, published on 4 Nov 2024. 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-2024-10523 in the wild and no public exploit code.

Affected product: TP-Link Tapo H100 IoT Smart Hub. 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-10523/ (Markdown: https://insights.sbomify.com/CVE-2024-10523/index.md)
```

## Sources

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

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