dbcve.org
TapoApplication · Tp Link

CVE-2023-38908

MEDIUM · 6.5 CVSS v3.1 Published 2023-08-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue in TPLink Smart Bulb Tapo series L530 before 1.2.4, L510E before 1.1.0, L630 before 1.0.4, P100 before 1.5.0, and Tapo Application 2.8.14 allows a remote attacker to obtain sensitive information via the TSKEP authentication function.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An information disclosure vulnerability in TP-Link Tapo smart home devices (L530, L510E, L630, P100) and the Tapo mobile application allows remote attackers to obtain sensitive information through the TSKEP authentication function. The vulnerability affects specific firmware versions before the fixes and can be exploited without authentication.

MitigationUpdate all affected TP-Link Tapo devices to the latest firmware versions (L530 1.2.4, L510E 1.1.0, L630 1.0.4, P100 1.5.0) and update the Tapo mobile application to version 2.8.14 or later.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TapoApplication
Affected:= 2.8.14
Tapo L530e FirmwareOperating system
Affected:= 1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Tapo mobile application version on iOS
    Open the App Store, go to the Tapo app page, and view the version number under the app name
    Affected if The installed version is earlier than 2.8.14
  2. Check Tapo mobile application version on Android
    Open Google Play Store, go to the Tapo app listing, and view the version number under the app name
    Affected if The installed version is earlier than 2.8.14
  3. Check Tapo L530e smart bulb firmware version
    Open the Tapo mobile app, select the L530e device, go to Device Settings, then Device Info, and note the Firmware Version
    Affected if The firmware version is earlier than 1.2.4
  4. Check Tapo L510E smart bulb firmware version
    Open the Tapo mobile app, select the L510E device, go to Device Settings, then Device Info, and note the Firmware Version
    Affected if The firmware version is earlier than 1.1.0
  5. Check Tapo L630 smart bulb firmware version
    Open the Tapo mobile app, select the L630 device, go to Device Settings, then Device Info, and note the Firmware Version
    Affected if The firmware version is earlier than 1.0.4
  6. Check Tapo P100 smart plug firmware version
    Open the Tapo mobile app, select the P100 device, go to Device Settings, then Device Info, and note the Firmware Version
    Affected if The firmware version is earlier than 1.5.0

The environment is affected if any Tapo mobile app version is earlier than 2.8.14, or if any of the specific device models (L530e, L510E, L630, P100) have firmware versions earlier than their respective fixed versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update all affected TP-Link Tapo devices to the latest firmware versions (L530 1.2.4, L510E 1.1.0, L630 1.0.4, P100 1.5.0) and update the Tapo mobile application to version 2.8.14 or later.

Recommended fix High confidence

Tapo L530: firmware >= 1.2.4 | Tapo L510E: firmware >= 1.1.0 | Tapo L630: firmware >= 1.0.4 | Tapo P100: firmware >= 1.5.0 | Tapo Application: version > 2.8.14

  1. Identify the specific Tapo device model (L530, L510E, L630, P100) or Tapo Application version in use
  2. For Tapo L530e: Upgrade firmware to version 1.2.4 or later
  3. For Tapo L510E: Upgrade firmware to version 1.1.0 or later
  4. For Tapo L630: Upgrade firmware to version 1.0.4 or later
  5. For Tapo P100: Upgrade firmware to version 1.5.0 or later
  6. For Tapo Application: Upgrade to a version newer than 2.8.14
  7. Verify the upgrade was successful and the TSKEP authentication vulnerability is resolved
Caveat Firmware updates may temporarily disconnect smart bulbs; ensure stable power during upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tapo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-38908 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-38908 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data