CVE-2022-39867
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 SHOW_PERSISTENT_BANNER 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 cloudNotificationManager.java allows unauthorized access to sensitive information through the SHOW_PERSISTENT_BANNER broadcast mechanism in SmartThings app versions prior to 1.7.89.0. Attackers can exploit this to read sensitive data without proper authentication or authorization checks.
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.
-
Check SmartThings app version on AndroidOpen Settings > Apps > SmartThings > App info or tap the app in the Play Store to view the version numberAffected if The displayed version is lower than 1.7.89.0
-
Check SmartThings app version on iOSOpen the App Store, search for SmartThings, or go to Settings > General > iPhone Storage > SmartThings to view versionAffected if The displayed version is lower than 1.7.89.0
-
Verify version via SmartThings appOpen the SmartThings app, go to Settings (gear icon) > About SmartThings to view the app versionAffected if The version shown is below 1.7.89.0
A user is affected if the installed SmartThings app version is lower than 1.7.89.0, as earlier versions contain the improper access control vulnerability in cloudNotificationManager.java for the SHOW_PERSISTENT_BANNER broadcast mechanism.
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 for the broadcast handler. If unable to upgrade immediately, consider disabling or restricting the SHOW_PERSISTENT_BANNER broadcast capability.
1.7.89.0 or later
- Open Google Play Store or Samsung Galaxy Store on the Android device
- Search for "SmartThings" in the app store
- Locate the SmartThings app in the search results
- Tap the "Update" button to update to the latest version (1.7.89.0 or later)
- Verify the update completed successfully by checking the app version in the app settings or store listing
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39867 — 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-39867 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