CVE-2022-30749
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 vulnerability in Smart Things prior to 1.7.85.25 allows local attackers to add arbitrary smart devices by bypassing login activity.
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 vulnerability in Smart Things versions prior to 1.7.85.25 allows local attackers to bypass authentication and add arbitrary smart devices to the system without proper authorization.
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.85.25CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Samsung SmartThings app on the deviceOpen the device's app drawer or settings menu and find the Samsung SmartThings application icon, or navigate to Settings > Apps > SmartThings on Android devicesAffected if The SmartThings app is installed on the device
-
Determine the installed SmartThings versionOn Android: Go to Settings > Apps > SmartThings > App info > Version. On iOS: Go to Settings > SmartThings > Version. Alternatively, long-press the app icon and select App info or tap the info icon to view version detailsAffected if Unable to retrieve a version number from the app settings
-
Compare the installed version to the vulnerable rangeExamine the version number displayed (format typically shows as three numbers like X.Y.Z) and compare it numerically to 1.7.85.25Affected if The displayed version is less than 1.7.85.25 (for example, 1.7.85.24, 1.7.80.0, or any version where the first number before the first dot is lower, or matches 1.7 but the number after the second dot is below 25)
-
Verify the version format if unclearIf the app displays only a build number or the version format is unclear, check the app's about section or release notes within the app menu for the full version stringAffected if The version cannot be confirmed as 1.7.85.25 or higher
The environment is affected if the Samsung SmartThings app version installed is numerically lower than 1.7.85.25, as versions prior to this contain the authentication bypass flaw allowing unauthorized device addition.
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.
dbcve · scoped1.7.85.25
Upgrade Smart Things to version 1.7.85.25 or later to remediate the access control bypass vulnerability.
SmartThings app version 1.7.85.25 or later
- Open your device's app store (Google Play Store or Apple App Store)
- Search for 'SmartThings' and check the current installed version
- If the installed version is older than 1.7.85.25, update the SmartThings app to the latest available version
- After updating, verify the app version shows 1.7.85.25 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30749 — 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-2022-30749 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