TP-Link Tapo H200 V1 IoT Smart Hub up to 1.4.0 cleartext storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.0 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in TP-Link Tapo H200 V1 IoT Smart Hub up to 1.4.0. Affected is an unknown function. This manipulation causes cleartext storage. This vulnerability is registered as CVE-2025-3442. It is feasible to perform the attack on the physical device. No exploit is available.
Details
A vulnerability has been found in TP-Link Tapo H200 V1 IoT Smart Hub up to 1.4.0 and classified as problematic. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a cleartext storage vulnerability. The CWE definition for the vulnerability is CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. As an impact it is known to affect confidentiality. The summary by CVE is:
This vulnerability exists in TP-Link Tapo H200 V1 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.
The advisory is shared at cert-in.org.in. This vulnerability is known as CVE-2025-3442 since 04/08/2025. The exploitation appears to be difficult. An attack has to be approached locally. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1555 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.tp-link.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 2.0VulDB Meta Temp Score: 2.0
VulDB Base Score: 2.0
VulDB Temp Score: 2.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Cleartext storageCWE: CWE-312 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: Yes
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
04/08/2025 🔍04/09/2025 🔍
04/09/2025 🔍
04/09/2025 🔍
Sources
Vendor: tp-link.comAdvisory: CIVN-2025-0072
Status: Not defined
CVE: CVE-2025-3442 (🔍)
GCVE (CVE): GCVE-0-2025-3442
GCVE (VulDB): GCVE-100-304105
Entry
Created: 04/09/2025 11:54Updated: 04/09/2025 15:28
Changes: 04/09/2025 11:54 (65), 04/09/2025 15:28 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.