dbcve.org
SmartthingsApplication · Samsung

CVE-2022-30747

MEDIUM · 5.5 CVSS v3.1 Published 2022-06-07
Fix available
A fix is available. Upgrade to 1.7.85.25 or later.
See remediation →
57/100
Remediation priority · Elevated
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
PendingIntent hijacking vulnerability in Smart Things prior to 1.7.85.25 allows local attackers to access files without permission via implicit Intent.

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

PendingIntent hijacking vulnerability in Samsung Smart Things Android app versions prior to 1.7.85.25. The app creates PendingIntents with implicit Intents (not specifying exact target components), allowing malicious local applications to intercept these intents and inherit the app's permissions to access files without proper authorization.

MitigationUpdate Smart Things Android application to version 1.7.85.25 or later which implements proper explicit Intent handling in PendingIntent creation to prevent intent hijacking.

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.85.25

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Locate the Samsung Smart Things app on your Android device
    Open your device Settings, navigate to Apps or Applications, then search for or locate 'SmartThings' in the list of installed applications.
    Affected if Unable to locate the SmartThings app indicates it may not be installed, or it may be installed under a different name.
  2. Check the installed version number
    In the Apps list, tap on SmartThings, then view the Version or Version information displayed on the app info screen. Alternatively, open the Google Play Store, search for SmartThings, and view the version under the app description.
    Affected if The displayed version number is less than 1.7.85.25.
  3. Verify the specific version against the affected range
    Compare the version number you found (for example, 1.7.85.24, 1.7.60.10, etc.) to the threshold version 1.7.85.25. Note that version comparison should treat it as a numeric comparison where any version below 1.7.85.25 is affected.
    Affected if Your installed version is any version prior to 1.7.85.25, such as 1.7.85.24 or earlier releases.
  4. Confirm the app is the official Samsung application
    Verify the app developer is listed as 'Samsung Electronics Co., Ltd.' in the app info screen under App info or in the Play Store listing to ensure you are checking the legitimate Samsung SmartThings app.
    Affected if The app is not the official Samsung SmartThings application, making this specific CVE not applicable to your installation.

You are affected if the Samsung Smart Things Android app version installed on your device is any version lower than 1.7.85.25.

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.85.25 or later
Fixed in 1.7.85.25
Interim mitigation

Update Smart Things Android application to version 1.7.85.25 or later which implements proper explicit Intent handling in PendingIntent creation to prevent intent hijacking.

Recommended fix Moderate confidence

SmartThings version 1.7.85.25 or later

  1. Open your device's app store (Google Play Store or Samsung Galaxy Store)
  2. Search for 'SmartThings' app
  3. If an update is available, tap 'Update' to install version 1.7.85.25 or later
  4. Alternatively, uninstall and reinstall the app to get the latest version
  5. After updating, verify the app version in the app settings to confirm you have version 1.7.85.25 or higher

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-2022-30747 — 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-30747 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