CVE-2025-1099: Information Disclosure Vulnerability in TP-Link Tapo C500 Wi-Fi Camera
First published: Mon Feb 10 2025(Updated: )
This vulnerability exists in Tapo C500 Wi-Fi camera due to hard-coded RSA private key embedded within the device firmware. An attacker with physical access could exploit this vulnerability to obtain cryptographic private keys which can then be used to perform impersonation, data decryption and man in the middle attacks on the targeted device.
Credit: vdisclose@cert-in.org.in
| Affected Software | Affected Version | How to fix |
|---|---|---|
| TP-Link Tapo C500 |
Remedy
Upgrade TP-Link Tapo C500 V1 to version 1.3.2 https://download.tplinkcloud.com/firmware/Tapo_C500v1_en_1.3.2_Build_250108_Rel.40063n_up_boot-signe... https://download.tplinkcloud.com/firmware/Tapo_C500v1_en_1.3.2_Build_250108_Rel.40063n_up_boot-signed_1737345124385.bin Upgrade TP-Link Tapo C500 V2 to version 1.0.6 http://download.tplinkcloud.com/firmware/Tapo_C500v1_en_1.3.2_Build_250108_Rel.40063n_up_boot-signed... http://download.tplinkcloud.com/firmware/Tapo_C500v1_en_1.3.2_Build_250108_Rel.40063n_up_boot-signed_1737345124385.bin
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2025-1099?
The severity of CVE-2025-1099 is considered high due to the exploitation of a hard-coded RSA private key in the TP-Link Tapo C500 camera.
How do I fix CVE-2025-1099?
To fix CVE-2025-1099, users should update the firmware of the TP-Link Tapo C500 camera to the latest version provided by the manufacturer.
What are the potential risks associated with CVE-2025-1099?
The risks associated with CVE-2025-1099 include unauthorized access to the camera's features and potentially compromising the security and privacy of the surveillance footage.
Who is affected by CVE-2025-1099?
CVE-2025-1099 affects users of the TP-Link Tapo C500 V1 and V2 Wi-Fi security cameras.
Is physical access required to exploit CVE-2025-1099?
Yes, physical access to the device is required to exploit CVE-2025-1099 due to the nature of the hard-coded RSA private key.
- agent/references
- agent/remedy
- agent/weakness
- agent/title
- agent/type
- agent/first-publish-date
- agent/author
- agent/source
- agent/severity
- agent/event
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/description
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- vendor/tp-link
- canonical/tp-link tapo c500