CVE-2022-39869
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 REMOVE_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 · moderate confidenceImproper access control vulnerability in SmartThings cloudNotificationManager.java allows unauthorized access to sensitive information via the REMOVE_PERSISTENT_BANNER broadcast due to missing or insufficient authorization validation, enabling attackers to bypass access controls.
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.
-
Identify if Samsung SmartThings app is installedCheck device for SmartThings application - on Android check Settings > Apps > SmartThings, or on iOS check Settings > SmartThings in the app libraryAffected if SmartThings app is present on the device
-
Determine installed SmartThings versionNavigate to SmartThings app settings: tap profile icon > Settings > About SmartThings > Version, or check in device app store listingAffected if Unable to retrieve version information from the app
-
Compare version against affected rangeCompare the installed version number to the affected range: any version lower than 1.7.89.0 is vulnerableAffected if Installed version is less than 1.7.89.0 (for example 1.7.85.0, 1.7.70.0, etc.)
-
Verify if REMOVE_PERSISTENT_BANNER functionality is accessibleThis check requires source code analysis or runtime monitoring of the app to observe if the REMOVE_PERSISTENT_BANNER broadcast action processes without authorization checks - typically not directly observable without debugging toolsAffected if App processes REMOVE_PERSISTENT_BANNER broadcast without validating user authorization (requires code review or dynamic analysis to confirm)
User is affected if Samsung SmartThings app version is installed and is lower than 1.7.89.0, enabling unauthorized access via the REMOVE_PERSISTENT_BANNER broadcast action.
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 to SmartThings version 1.7.89.0 or later which implements proper access control checks on the REMOVE_PERSISTENT_BANNER broadcast action.
1.7.89.0 or later
- Open the Google Play Store (Android) or App Store (iOS) on your device
- Search for "SmartThings" and select the official Samsung SmartThings app
- Tap "Update" to install version 1.7.89.0 or later
- Alternatively, enable automatic app updates in your device settings to ensure future security patches are applied
- After updating, verify the version by going to Settings > Apps > SmartThings and checking the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39869 — 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-39869 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