CVE-2021-25378
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 · uneditedImproper access control of certain port in SmartThings prior to version 1.7.63.6 allows remote temporary denial of service.
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 confidenceImproper access control on a certain port in Samsung SmartThings prior to version 1.7.63.6 allows remote unauthenticated attackers to cause temporary denial of service. The vulnerability stems from insufficient restrictions on network ports, enabling external entities to trigger service disruption.
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< 1.7.63.6CVSS 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
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SmartThings deploymentIdentify whether Samsung SmartThings hub hardware or software is deployed in your environment. This may appear as a SmartThings Hub device on your network or as the SmartThings application.Affected if SmartThings hub or application is present in the environment
-
Check SmartThings versionAccess the SmartThings hub settings or mobile application and navigate to the version information section. For hubs, this is typically found in the device settings or about menu. For the mobile app, check the app version in your device's app store or within the app settings.Affected if The installed version number is lower than 1.7.63.6
-
Identify exposed network portsScan your network for open ports on the SmartThings hub device. Use network scanning tools (such as nmap) to identify which ports are listening on the hub IP address. Document any ports that are accessible from external networks.Affected if Network ports on the SmartThings device are exposed to untrusted networks without firewall restrictions
-
Verify port access controlsReview firewall rules, router configurations, or network ACLs that govern access to the SmartThings hub. Confirm whether inbound access to the hub ports is restricted to authorized internal devices or networks only.Affected if Network ports on the SmartThings hub are accessible from untrusted/external networks without proper authentication or IP restrictions
You are affected if a Samsung SmartThings installation version lower than 1.7.63.6 is present AND its network ports are exposed to untrusted networks without access controls.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data1.7.63.6
Update SmartThings to version 1.7.63.6 or later to patch the improper access control vulnerability. If immediate patching is not feasible, consider network segmentation to limit exposure of the SmartThings infrastructure.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25378 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-25378 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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