CVE-2022-39870
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 cloudNotificationManager.java SmartThings prior to version 1.7.89.0 allows attackers to access sensitive information via PUSH_MESSAGE_RECEIVED 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 · high confidenceImproper access control in SmartThings cloudNotificationManager.java allows unauthenticated attackers to access sensitive information through the PUSH_MESSAGE_RECEIVED broadcast. The broadcast receiver lacks proper authorization checks before disclosing data, enabling information disclosure to any application or attacker that can send the specific broadcast message.
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.89.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm SmartThings app is installedOn the Android device, go to Settings > Apps > Apps and look for 'SmartThings' in the application list, or run 'adb shell pm list packages | grep smartthings'Affected if The SmartThings application is found on the device
-
Identify installed SmartThings versionIn Settings > Apps > Apps > SmartThings > App info, note the version number displayed under the app name, or run 'adb shell dumpsys package com.samsung.android.app.samsungwisebroker | grep versionName'Affected if A version number is displayed that can be compared to 1.7.89.0
-
Compare version against vulnerable rangeCompare the identified version number to 1.7.89.0 using semantic version comparisonAffected if The installed version is lower than 1.7.89.0 (for example, 1.7.88.0, 1.7.75.2, etc.)
The device is affected if Samsung SmartThings app is installed with a version lower than 1.7.89.0, as this version range contains the vulnerable cloudNotificationManager.java component lacking authorization checks on the PUSH_MESSAGE_RECEIVED broadcast.
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.89.0
Upgrade SmartThings to version 1.7.89.0 or later which contains proper access control validation on the PUSH_MESSAGE_RECEIVED broadcast receiver to verify caller authorization before returning sensitive data.
SmartThings version 1.7.89.0 or later
- Open your device's app store (Google Play Store or Apple App Store)
- Search for "SmartThings" app
- Update the SmartThings application to version 1.7.89.0 or later
- Verify the update was successful by checking the app version in the app settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39870 — 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-39870 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