CVE-2022-22286
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 · uneditedA vulnerability using PendingIntent in Bixby Routines prior to version 3.1.21.8 in Android R(11.0) and 2.6.30.5 in Android Q(10.0) allows attackers to execute privileged action by hijacking and modifying the intent.
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 confidenceThis is a PendingIntent hijacking vulnerability in Samsung's Bixby Routines app. PendingIntent allows one app to pass an intent to another app for execution, but when improperly protected, attackers can intercept and modify the intent before execution, allowing privileged actions to be performed in the context of the vulnerable app.
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< 3.1.21.8< 2.6.30.5CVSS 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
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 Bixby Routines is installedOpen device Settings, go to Apps, and search for 'Bixby Routines' or locate it in the app list. Alternatively, use ADB: adb shell pm list packages | grep bixbyAffected if The Bixby Routines app is not found on the device, meaning this CVE does not apply
-
Determine Android OS versionGo to Settings > About Phone > Android version, or use ADB: adb shell getprop ro.build.version.releaseAffected if Android 11 (R) or Android 10 (Q) is running; other Android versions use different version thresholds per the advisory
-
Retrieve Bixby Routines version numberIn Settings > Apps > Bixby Routines > App info, note the version displayed (e.g., version 3.1.05.8). Or use ADB: adb shell dumpsys package com.samsung.android.app.routinesAffected if Unable to determine the installed version number for comparison
-
Compare against affected version rangeIf on Android 11 (R): check if version is less than 3.1.21.8. If on Android 10 (Q): check if version is less than 2.6.30.5. Versions meet the format X.Y.Z.WAffected if Installed version is lower than 3.1.21.8 on Android 11, or lower than 2.6.30.5 on Android 10, indicating the vulnerable version is present
The device is affected if Bixby Routines is installed and the version is below 3.1.21.8 on Android 11 or below 2.6.30.5 on Android 10.
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 · scoped2.6.30.53.1.21.8
Update Bixby Routines to version 3.1.21.8 or higher on Android R (11.0) and version 2.6.30.5 or higher on Android Q (10.0) to receive the security patch.
Bixby Routines 3.1.21.8 (Android 11.0) or 2.6.30.5 (Android 10.0)
- Open the Google Play Store on your Samsung device
- Search for "Bixby Routines" or "Samsung Bixby Routines"
- Tap Update to install version 3.1.21.8 or higher (for Android 11.0 devices)
- For Android 10.0 devices, ensure you update to version 2.6.30.5 or higher
- Verify the update was successful by checking the app version in Settings > Apps > Bixby Routines
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing2.0 h
- Review / QA1.0 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-22286 — 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-22286 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