CVE-2021-25352
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 · uneditedUsing PendingIntent with implicit intent in Bixby Voice prior to version 3.0.52.14 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 confidenceBixby Voice creates PendingIntents with implicit intents, allowing a malicious application to intercept and hijack these intents. Since PendingIntents are mutable in older Android versions, an attacker can modify the intent's extras or redirect the action to execute privileged operations under 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.0.52.14CVSS 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 if Bixby Voice is installedOpen the device Settings > Apps and search for 'Bixby Voice', or use ADB command: `adb shell pm list packages | grep bixby`Affected if Bixby Voice package (com.samsung.android.bixby.agent) is not found on the device, then the device is not affected
-
Determine installed Bixby Voice versionOpen Settings > Apps > Bixby Voice > App info, or use ADB command: `adb shell dumpsys package com.samsung.android.bixby.agent | grep versionName`Affected if Unable to retrieve version information; ensure you have sufficient permissions to query the package
-
Compare version to affected rangeReview the version number obtained from the previous step. The affected range is any version lower than 3.0.52.14 (for example, 3.0.45.12, 2.1.33.5, etc.)Affected if Installed version is a three-part number where the first part is less than 3, or equals 3 but the second part is less than 0, or equals 3.0 but the third part is less than 52, or equals 3.0.52 but the build number is less than 14
-
Confirm Android OS version contextCheck Settings > About Phone > Android version. The vulnerability impact is heightened on Android 11 (API 30) and earlier due to mutable PendingIntent behavior, though the vulnerability exists across versionsAffected if This step provides context only; the version check in step 3 is the definitive determination of whether the CVE applies
If Bixby Voice is installed and its version number is lower than 3.0.52.14, the device 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.
From vendor data3.0.52.14
Update Bixby Voice to version 3.0.52.14 or later, which should replace implicit intents with explicit intents when creating PendingIntents and use FLAG_IMMUTABLE.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25352 — 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-2021-25352 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