CVE-2022-30716
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 · uneditedUnprotected broadcast in sendIntentForToastDumpLog in DisplayToast prior to SMR Jun-2022 Release 1 allows untrusted applications to access toast message information from device.
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 confidenceSamsung's DisplayToast component contains an unprotected broadcast in the sendIntentForToastDumpLog function that allows any untrusted application to receive toast message data from the device, enabling information disclosure of content displayed in toast notifications.
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= 10.0= 11.0= 12.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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Version is 10.0, 11.0, or 12.0 specifically (not later)
-
Check Samsung security patch levelGo to Settings > About Phone > Software information > Security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if Patch level is earlier than June 2022 (for example, May 2022 or earlier)
-
Verify DisplayToast component presenceCheck system app list for packages containing 'DisplayToast' using 'pm list packages | grep -i toast' via ADB, or inspect /system/priv-app/ for DisplayToast.apkAffected if The DisplayToast system app is installed and the unprotected broadcast receiver in sendIntentForToastDumpLog is exposed
Device is affected if running Android 10.0, 11.0, or 12.0 with a Samsung security patch level before June 2022, as the unprotected toast message broadcast remains accessible to untrusted applications.
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 · scopedApply the Samsung SMR Jun-2022 Release 1 or later security update which adds proper permission protection (signature-level) to the toast message broadcast to restrict access to trusted system components only.
Samsung SMR Jun-2022 Release 1 security patch (or later)
- Navigate to Settings on the Samsung device
- Go to About Phone (or About Device)
- Select Software Update (or Software Information)
- Check the Security patch level - verify it shows a date of June 2022 or later (SMR Jun-2022 Release 1)
- If a newer update is available, download and install it to receive the security fix
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Testing6.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,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30716 — 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-30716 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