dbcve.org
SmartthingsApplication · Samsung

CVE-2022-39868

HIGH · 7.5 CVSS v3.1 Published 2022-10-07
Fix available
A fix is available. Upgrade to 1.7.89.0 or later.
See remediation →
84/100
Remediation priority · High
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 access control vulnerability in GedSamsungAccount.kt SmartThings prior to version 1.7.89.0 allows attackers to access sensitive information via implicit broadcast.

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 access control vulnerability in the SmartThings Android application's GedSamsungAccount.kt component allows malicious apps on the same device to intercept sensitive information via implicit Android broadcast communications. This exposes account-related data due to inadequate permission checks on the inter-component communication.

MitigationUpgrade SmartThings Android application to version 1.7.89.0 or later which contains the fix for proper access control on the broadcast component.

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

CVSS:3.1/AV:N/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. Verify SmartThings Android app is installed
    Open device Settings > Apps > SmartThings, or run 'adb shell pm list packages | grep smartthings' to check if the package com.samsung.android.unicouplesmartthings is present
    Affected if The SmartThings Android application is installed on the device
  2. Check installed SmartThings version
    Go to Settings > Apps > SmartThings > App info, or use 'adb shell dumpsys package com.samsung.android.unicouplesmartthings | grep versionName' to retrieve the exact version string
    Affected if The version displayed is lower than 1.7.89.0 (e.g., 1.7.88.23, 1.7.75.0, etc.)
  3. Confirm the GedSamsungAccount component exists
    Decompile the APK using apktool and inspect /smali/com/samsung/android/ged/samsung/account/GedSamsungAccount.kt or use 'aapt dump badging smartthings.apk | grep activity' to list components
    Affected if The GedSamsungAccount broadcast receiver is present in the application manifest with an implicit intent filter and no proper permission protection
  4. Verify broadcast receiver permission configuration
    Examine the AndroidManifest.xml for the GedSamsungAccount receiver declaration; check if android:exported="true" and no android:permission attribute is set, or use 'adb shell dumpsys package' to inspect receiver permissions
    Affected if The broadcast receiver is exported without a permission requirement, allowing any app on the device to receive the broadcast

The device is affected if the SmartThings Android application version is below 1.7.89.0 and the GedSamsungAccount broadcast component is exported without proper permission checks, enabling a malicious local app to intercept sensitive account data.

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.89.0 or later
Fixed in 1.7.89.0
Interim mitigation

Upgrade SmartThings Android application to version 1.7.89.0 or later which contains the fix for proper access control on the broadcast component.

Recommended fix High confidence

SmartThings app version 1.7.89.0 or later

  1. Open Google Play Store (Android) or Apple App Store (iOS) on your device
  2. Search for "SmartThings" in the app store
  3. Locate the SmartThings app and check the current version number
  4. If the available version is 1.7.89.0 or later, tap Update to install the security fix
  5. If automatic updates are enabled, the app should update automatically once the fixed version is released
  6. Verify the update was successful by checking the app version in Settings > Apps > SmartThings > Version
  7. Alternatively, visit the Samsung Galaxy Store or Samsung's official support page to download the latest version

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

Fix this in Smartthings Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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