CVE-2022-30758
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 · uneditedImplicit Intent hijacking vulnerability in Finder prior to SMR Jul-2022 Release 1 allow allows attackers to access some protected information 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 · moderate confidenceThis is an implicit Intent hijacking vulnerability in Samsung's Finder application. Implicit Intents (broadcasts without specified target receivers) in the Finder app could be intercepted by malicious applications that register BroadcastReceivers, allowing unauthorized access to protected information that the Finder app was broadcasting.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify Samsung Finder app is installedCheck if the package com.sec.android.app.finder exists on the device (via adb: pm list packages | grep finder, or check in Settings > Apps)Affected if The Finder app is present on the device
-
Confirm Android OS version is 10, 11, or 12Check Android version in Settings > About Phone > Android version (or via adb: getprop ro.build.version.release)Affected if Android version equals 10.0, 11.0, or 12.0
-
Check device security patch levelCheck Settings > About Phone > Security patch level, or via adb: getprop ro.build.version.security_patchAffected if Security patch level is earlier than July 2022 (the SMR containing the fix)
-
Verify Finder app versionCheck the installed version of Samsung Finder in Settings > Apps > Finder > Version infoAffected if Cannot verify fix via app version alone; must rely on patch level
A user is affected if they have a Samsung device with the Finder app installed, running Android 10, 11, or 12, and the device security patch level is earlier than the July 2022 Samsung SMR.
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 (Security Monthly Release) July 2022 or later patch. Organizations should ensure fleet devices receive monthly security updates and verify patch compliance through mobile device management (MDM) solutions.
SMR Jul-2022 Release 1 (July 2022 Security Patch Level)
- Open Settings on the Samsung device
- Navigate to 'Software update' or 'About phone'
- Tap on 'Check for updates' or 'Download updates manually'
- Ensure the device downloads and installs the July 2022 security update (SMR Jul-2022 Release 1)
- Verify the update was installed by checking the security patch level in Settings > About phone > Software information > Security patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30758 — 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-30758 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