dbcve.org
AndroidOperating system · Google

CVE-2022-30722

CRITICAL · 9.8 CVSS v3.1 Published 2022-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Implicit Intent hijacking vulnerability in Samsung Account prior to SMR Jun-2022 Release 1 allows attackers to bypass user confirmation of Samsung Account.

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 confidence

This is an implicit Intent hijacking vulnerability in Samsung's Android Account management application. Attackers can register a malicious component to intercept implicit intents meant for Samsung Account, allowing them to bypass user confirmation prompts and perform unauthorized account actions. This represents a critical failure in Android inter-component communication security.

MitigationUpdate Samsung devices to SMR June-2022 Release 1 or later to receive the patched Samsung Account application. For enterprise environments, ensure MDM policies enforce OS/security updates on Samsung devices.

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
AndroidOperating system
Affected:= 10.0= 11.0= 12.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm device is a Samsung device
    Run 'getprop ro.product.brand' or check device manufacturer in Settings > About Phone
    Affected if Device brand is not Samsung (this vulnerability only affects Samsung devices)
  2. Verify Android version is affected
    Check Android version in Settings > About Phone > Android version, or run 'getprop ro.build.version.release'
    Affected if Android version is 10.0, 11.0, or 12.0 (these are the versions with vulnerable Samsung Account app)
  3. Confirm Samsung Account application is installed
    Check for Samsung Account app in app settings or list all packages with 'pm list packages | grep samsung.account'
    Affected if Samsung Account app is installed (the vulnerability exists within this app)
  4. Check Samsung Account app version
    Open Settings > Accounts and backup > Accounts > Samsung Account, or use 'dumpsys package com.amsung.android.samsungaccount' to view version info
    Affected if Version is present and corresponds to pre-June 2022 release (vulnerable versions lack proper intent filtering)
  5. Verify if intent protection is disabled
    Review app permissions for Samsung Account - check if any third-party apps have permission to intercept intents (this is not a config check but indicates the attack surface)
    Affected if Multiple or unknown apps have unusual inter-app communication permissions with Samsung Account

A user is affected if they have a Samsung device running Android 10, 11, or 12 with the Samsung Account application installed and the vulnerability is present in the pre-patched version of that app.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Samsung devices to SMR June-2022 Release 1 or later to receive the patched Samsung Account application. For enterprise environments, ensure MDM policies enforce OS/security updates on Samsung devices.

Recommended fix High confidence

SMR Jun-2022 Release 1 (Android 10/11/12 security update)

  1. Check for system updates on the Samsung device by going to Settings > Software Update > Download and install
  2. Ensure the device receives the SMR Jun-2022 Release 1 or later security patch
  3. Alternatively, update the Samsung Account app through Galaxy Store or Google Play Store to the latest version after the June 2022 update
  4. Verify the device is running Android security patch level June 2022 or later via Settings > About phone > Software information > Security patch level

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-30722 — 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-30722 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