Key disclosure via hard-coded firmware private key
Published Feb 10, 2025 · Updated Feb 14, 2025
Hard-coded key storage in TP-Link Tapo C500 firmware allows physically proximate attackers to obtain embedded RSA private keys. The device firmware embeds an unchangeable RSA private key instead of protecting a device-specific secret outside the extractable image. Physical access to an affected V1 or V2 camera is required; the recovered key enables device impersonation, traffic decryption, and man-in-the-middle attacks.
Summary
What happened
Hard-coded key storage in TP-Link Tapo C500 firmware allows physically proximate attackers to obtain embedded RSA private keys. The device firmware embeds an unchangeable RSA private key instead of protecting a device-specific secret outside the extractable image. Physical access to an affected V1 or V2 camera is required; the recovered key enables device impersonation, traffic decryption, and man-in-the-middle attacks.
The record
- CVE
- CVE-2025-1099
- Published
- Feb 10, 2025
- Updated
- Feb 14, 2025
- Vendor
- TP-Link
- Product
- Tapo C500
- Classifications
- CWE-321, T1552.004
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 2025CVE publishedPublication date reported by the CVE source.
- Feb 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<=1.0.2
- Affected versionversion=<=1.1.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo