dbcve.org
SmartthingsApplication · Samsung

CVE-2025-2233

HIGH · 8.8 CVSS v3.0 Published 2025-03-11
Fix available
A fix is available. Upgrade to 0.55.5 or later.
See remediation →
93/100
Remediation priority · Urgent
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
Samsung SmartThings Improper Verification of Cryptographic Signature Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of Samsung SmartThings. Authentication is not required to exploit this vulnerability. The specific flaw exists within the Hub Local API service, which listens on TCP port 8766 by default. The issue results from the lack of proper verification of a cryptographic signature. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-25615.

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 · high confidence

Samsung SmartThings Hub contains a vulnerability in the Local API service listening on TCP port 8766. The flaw allows network-adjacent attackers to bypass authentication due to improper verification of cryptographic signatures. This enables unauthenticated attackers to interact with the Hub's local API as if they were authenticated users.

MitigationRestrict network access to port 8766 through firewall rules or network segmentation. Apply vendor-provided firmware updates when available. Monitor for unauthorized access attempts to the Local API endpoint.

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:< 0.55.5

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
High
Availability
High

CVSS:3.0/AV:A/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 Hub version
    Check the installed firmware or application version through the SmartThings app or hub settings interface. Compare the version number against the affected range: versions below 0.55.5 are vulnerable.
    Affected if The installed version is below 0.55.5
  2. Verify Local API service is running
    Scan the hub or local network for TCP port 8766 to confirm the Local API service is listening. Use network scanning tools such as netstat, nmap, or similar to detect open ports on the hub device.
    Affected if Port 8766 is open and listening on the SmartThings Hub
  3. Assess network accessibility of port 8766
    Determine if port 8766 is reachable from network-adjacent devices. Check firewall configurations, router/access point settings, and network segmentation to see if the hub is exposed to unauthenticated network attackers.
    Affected if Port 8766 is accessible from untrusted network segments or external devices without authentication

The environment is affected if the SmartThings Hub runs a version below 0.55.5 AND has the Local API service on TCP port 8766 accessible to network-adjacent attackers.

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 0.55.5 or later
Fixed in 0.55.5
Interim mitigation

Restrict network access to port 8766 through firewall rules or network segmentation. Apply vendor-provided firmware updates when available. Monitor for unauthorized access attempts to the Local API endpoint.

Recommended fix Moderate confidence

0.55.5 or later

  1. Open the SmartThings application or web interface
  2. Navigate to the Hub settings or device settings
  3. Check the current firmware version under Hub information
  4. If the version is below 0.55.5, initiate a firmware update
  5. Wait for the update to complete and verify the new version is 0.55.5 or later

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

Fix this in Smartthings Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2233 — 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-2025-2233 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