TP-Link Tapo L530E (L530E)
From Wiki-IoT
Revision as of 12:46, 25 October 2026 by Xiabolili (talk | contribs) (Reverting an unintended overwrite; restoring the original classification made by 20232812jiaoyijia)
(diff) β Older revision | Latest revision (diff) | Newer revision β (diff)
| TP-Link Tapo L530E (L530E) | ||
|---|---|---|
|
Security Grade
Calculator v
|
TP-Link Tapo L530E (L530E)
Brand: TP-Link (Parent: TP-Link Systems Inc.) Category: Smart Wi-Fi bulb (E27, colour) • Model / Gen: L530E Release Date: 2021-06-01 • Status: In sale Classification Date: • Official Website | |
Contents
Security Evaluation
1. Device Security
| Criterion | Value | Proof | Comment |
|---|---|---|---|
| Known hardware tampering | Rare | π Proof | No documented hardware tamper shortcut, but the bulb is a sealed unit whose flash can be dumped after physical disassembly. |
| Known vulnerabilities | Very common | [1] [2] [3] π Proof | Four CVEs cover this exact model: replayed session key (7.5), auth code leak over UDP, TSKEP authentication leak and static IV in AES-128-CBC. |
| Prior attacks | Rare | π Proof | Researchers demonstrated taking over the bulb to reach other household devices, but no in-the-wild campaign or KEV entry. |
| Updatability | Very common | π Proof | All four issues are fixed in firmware 1.2.4; the bulb updates through the Tapo app. |
| Category Score | Score: 2 / 3 | ||
2. System Security
| Criterion | Value | Proof | Comment |
|---|---|---|---|
| Authentication with other systems | No | π Proof | There is no device-to-device authentication model; trust rests entirely on a cloud session key that can be replayed. |
| Communications | Encrypted with obselete encryption | π Proof | Traffic is AES-128-CBC encrypted but with a static IV and a replayable session key, which is obsolete use of a sound cipher. |
| Storage | No encryption | π Proof | No local storage and no secure element; credentials sit in app storage and are recoverable through the TSKEP flaws. |
| Category Score | Score: 3 / 3 | ||
3. User Authentication
| Criterion | Value | Proof | Comment |
|---|---|---|---|
| Account management | Absent | π Proof | The bulb has no account management of its own; it inherits the single Tapo cloud account with no roles or separation. |
| Authentication | Absent | π Proof | No authentication on the local control protocol, so any host on the same network that knows the message format can drive the bulb. |
| Brute-force protection | Absent | π Proof | No brute-force protection on the local protocol and the UDP authentication code can be captured rather than guessed. |
| Event logging | Absent | π Proof | No access log on the device and no export of authentication events; the app only shows on/off history. |
| Passwords | Default/Common/Easy to guess | π Proof | No local credential at all; the device depends on the cloud account password, which never rotates per device. |
| Category Score | Score: 3 / 3 | ||
Technical Specifications
| Property | Details |
|---|---|
| Operating System & App | Proprietary (Tapo firmware) (Companion App: Tapo) |
| Hardware (CPU / GPU) | CPU: • GPU: |
| Memory & Storage | Memory: • Storage: |
| Power, Battery & Charging | Battery: • Power: • Charging: |
| Display & Camera | Display: • Camera: |
| Sound & Connectivity | Sound: • Connectivity: Wi-Fi 2.4 GHz, Bluetooth LE (setup only) |
| Physical (Dimensions & Mass) | Dimensions: • Mass: |