SmartthingsApplication · Samsung

CVE-2021-25508

CRITICAL · 9.8 CVSS v3.1 Published 2021-11-05
Fix available
A fix is available. Upgrade to 1.7.73.22 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
Improper privilege management vulnerability in API Key used in SmartThings prior to 1.7.73.22 allows an attacker to abuse the API key without limitation.

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

Improper privilege management vulnerability in the SmartThings API key authentication mechanism prior to version 1.7.73.22 allows the API key to be abused without any limitation, likely providing unrestricted access or bypassing proper authorization controls.

MitigationUpdate SmartThings SDK/application to version 1.7.73.22 or later to obtain the patched API key privilege controls; rotate all potentially compromised API keys as a precautionary measure.

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
SmartthingsApplication
Affected:< 1.7.73.22

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify SmartThings installation
    Locate any Samsung SmartThings SDK, application, or related software installed in your environment. Check installed programs, application directories, or dependency listings for 'SmartThings' components.
    Affected if SmartThings software is present in the environment
  2. Determine SmartThings version
    Use system tools to query the installed version of SmartThings (such as via package manager, application info, or SDK metadata). Record the exact version number reported.
    Affected if Version is less than 1.7.73.22 or cannot be determined (treat as vulnerable)
  3. Verify API key usage
    Inspect your application configurations, environment variables, or credential storage for active SmartThings API keys. Identify where and how the API key is being used for authentication.
    Affected if API keys for SmartThings are actively configured or in use
  4. Assess API key privilege scope
    Review API key permissions and access controls configured for SmartThings. Check whether the key has unrestricted access or limited privileges assigned.
    Affected if API key appears to have unrestricted or unbounded privileges beyond what is intended

You are affected if SmartThings version is below 1.7.73.22 and you have active API keys in use, as the privilege management flaw allows API key abuse without proper limitation.

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
Upgrade available Upgrade to 1.7.73.22 or later
Fixed in 1.7.73.22
Interim mitigation

Update SmartThings SDK/application to version 1.7.73.22 or later to obtain the patched API key privilege controls; rotate all potentially compromised API keys as a precautionary measure.

Recommended fix High confidence

SmartThings app version 1.7.73.22 or later

  1. Open the Google Play Store (Android) or Apple App Store (iOS) on your mobile device
  2. Search for 'SmartThings' in the store
  3. If an update is available, tap 'Update' to install version 1.7.73.22 or later
  4. Alternatively, enable automatic app updates in your device settings to ensure you receive future security patches
  5. After updating, verify the app version by going to SmartThings app > Settings > About device to confirm version 1.7.73.22 or higher is installed

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

Fix this in Smartthings Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2021-25508 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