dbcve.org
AndroidOperating system · Google

CVE-2022-30756

HIGH · 7.8 CVSS v3.1 Published 2022-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 Finder prior to SMR Jul-2022 Release 1 allow allows attackers to launch certain activities with privilege of Finder.

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 Finder application on Android devices. The vulnerability allows a malicious application to intercept implicit Intents (broadcast messages) intended for the Finder app and launch activities with Finder's elevated system privileges, potentially achieving privilege escalation.

MitigationApply the Samsung SMR (Security Maintenance Release) July 2022 Update 1 or later to affected devices, which patches the implicit Intent handling in the Finder application.

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

CVSS:3.1/AV:L/AC:L/PR:L/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 Android device
    Check the device manufacturer and model in Settings > About Phone > Model Number, or run 'getprop ro.product.manufacturer' via ADB
    Affected if Device is not made by Samsung (this vulnerability affects only Samsung's Finder app)
  2. Verify Android version is in affected range
    Check Settings > About Phone > Android Version, or run 'getprop ro.build.version.release' via ADB
    Affected if Android version is 10, 11, or 12 (exact versions = 10.0, = 11.0, = 12.0)
  3. Confirm Samsung Finder application is installed
    Check Settings > Apps > Finder, or run 'pm list packages | grep finder' via ADB to list packages containing 'finder'
    Affected if Package com.sec.android.app.finder is installed on the device
  4. Check Finder app version against fixed release
    In Settings > Apps > Finder > App Info, note the version name and version code. Compare against the Samsung SMR July 2022 Update 1 fixed version for your specific model
    Affected if Finder version is older than the patched version released in July 2022 SMR Update 1
  5. Verify SMR update has been applied
    Check Settings > About Phone > Software Information > Build Number. The SMR (Samsung Maintenance Release) is indicated in the build number (e.g., SMR-xx-1 for July). Alternatively, check if the latest security patch level is July 2022 or later in Settings > About Phone > Security Patch Level
    Affected if Security Patch Level is earlier than July 2022 or SMR update has not been installed

A Samsung device on Android 10, 11, or 12 with the Finder app installed and a security patch level before July 2022 is likely affected by this implicit Intent hijacking vulnerability.

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

Apply the Samsung SMR (Security Maintenance Release) July 2022 Update 1 or later to affected devices, which patches the implicit Intent handling in the Finder application.

Recommended fix Moderate confidence

SMR Jul-2022 Release 1 or later

  1. Verify the device is running Android 10, 11, or 12 by navigating to Settings > About Phone > Android version
  2. Navigate to Settings > Software Update on the Samsung device
  3. Check for and download the July 2022 security update (SMR Jul-2022 Release 1) or later
  4. After updating the system, open Galaxy Store or Google Play Store
  5. Search for and update the Samsung Finder application to the latest available version
Caveat Security patches typically do not introduce breaking changes; however, availability may vary by carrier and device model

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

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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