CVE-2022-30754
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 AppLinker prior to SMR Jul-2022 Release 1 allow allows attackers to launch certain activities with privilege of AppLinker.
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 AppLinker application (a system app managing deep links). The flaw allows a malicious local application to intercept or hijack implicit Intents sent by AppLinker, enabling the attacker to launch specific activities with the elevated privileges of the AppLinker system app, achieving privilege escalation.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device is a Samsung deviceCheck the device manufacturer by reviewing the system properties or settings - look for Samsung as the OEMAffected if The device is not manufactured by Samsung, as AppLinker is a Samsung-specific system app
-
Check Android versionNavigate to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if Android version is 10.0, 11.0, or 12.0 (exactly matching the affected versions listed)
-
Locate AppLinker applicationCheck for the presence of the AppLinker package (com.samsung.android.applinker) in the system app directory or via package manager command 'pm list packages | grep applinker'Affected if AppLinker package exists on the device
-
Check AppLinker versionRun 'dumpsys package com.samsung.android.applinker' via ADB to retrieve the installed version informationAffected if The installed version has not received the July 2022 SMR fix (compare against the fixed version in Samsung security bulletins)
A Samsung device running Android 10.0, 11.0, or 12.0 with an unpatched version of the AppLinker system app is affected by this vulnerability.
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 Maintenance Release) for July 2022 or later, which contains the fix for this vulnerability in AppLinker.
Samsung SMR Jul-2022 Release 1 or later (Android 10/11/12 security patch)
- Open Settings on the Samsung device
- Scroll down and tap on Software Update
- Tap on Download and Install to check for available updates
- If the July 2022 SMR (Security Maintenance Release) or later is available, download and install it
- Restart the device after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation0.5 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30754 — 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-30754 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