CVE-2022-22292
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 dynamic receiver in Telecom prior to SMR Feb-2022 Release 1 allows untrusted applications to launch arbitrary activity.
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 confidenceAn unprotected dynamic BroadcastReceiver in Android's Telecom system service prior to Samsung's Feb-2022 SMR allows any untrusted application to send intents that can launch arbitrary activities within the Telecom component. This bypasses the normal permission model that should restrict such activity launches to privileged system components.
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.
-
Check Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if Version equals 10.0, 11.0, or 12.0 (exact match)
-
Check security patch levelGo to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shellAffected if Patch level is earlier than 2022-02-01 (for Samsung devices) or if on non-Samsung Android, no patch available since this was Samsung-specific
-
Identify device manufacturerGo to Settings > About Phone > Manufacturer, or run 'getprop ro.product.manufacturer' via ADB shellAffected if Device is a Samsung brand (the vulnerability existed in Samsung's implementation of Android Telecom)
-
Verify Telecom component exposureUse a security scanner app or ADB to check if the Telecom component's dynamic BroadcastReceiver accepts intents from untrusted apps without permission checksAffected if The Telecom service BroadcastReceiver accepts intents from any application without verifying caller permissions
You are affected if running Android 10.0, 11.0, or 12.0 on a Samsung device with a security patch level before February 2022, where the Telecom component's BroadcastReceiver lacks permission enforcement.
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 Feb-2022 Release 1 or later security patch, which adds proper permission checks to the dynamic receiver to prevent unauthorized activity invocation from untrusted apps.
Samsung SMR Feb-2022 Release 1 (Android 10, 11, 12)
- Check current Android version on the device in Settings > About Phone
- Check for system updates in Settings > Software Update
- Download and install the Samsung SMR Feb-2022 Release 1 or later security update
- Restart the device after the update completes
- Verify the security patch level in Settings > About Phone > Software Information matches February 2022 or later
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-22292 — 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-22292 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