CVE-2021-25401
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 · uneditedIntent redirection vulnerability in Samsung Health prior to version 6.16 allows attacker to execute privileged action.
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 confidenceIntent redirection vulnerability in Samsung Health app prior to version 6.16 allows a malicious app to intercept or redirect intents containing sensitive data or trigger privileged actions. This occurs when the app improperly handles implicit intents or fails to validate the source of incoming intents, enabling a local attacker to hijack the intent flow and execute operations with elevated privileges.
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< 6.16CVSS 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.
-
Verify Samsung Health is installedOpen Settings > Apps on the Samsung device and look for Samsung Health, or run 'adb shell pm list packages | grep samsung.health' if ADB is availableAffected if Samsung Health appears in the installed apps list
-
Determine the installed version of Samsung HealthIn Settings > Apps > Samsung Health > App info, locate the version number displayed (usually near the top as 'Version' or 'App version')Affected if A version number is shown and is less than 6.16
-
Confirm the version is in the affected rangeCompare the installed version number to 6.16. Note that version codes may appear as '6.15.x' or similar format - any version before 6.16 is affectedAffected if The installed version is 6.15.x, 6.14.x, or any earlier version number
-
Check for updates via Galaxy StoreOpen Galaxy Store, search for Samsung Health, and check if an update to version 6.16 or later is availableAffected if Galaxy Store shows an available update to version 6.16 or later, indicating the current version is older
A device is affected if Samsung Health is installed and its installed version is below 6.16, as versions prior to 6.16 contain the intent redirection vulnerability that could allow a malicious local app to intercept sensitive intents or trigger privileged actions.
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 data6.16
Update Samsung Health to version 6.16 or later. If unable to update, minimize exposure by avoiding use of the app until patched.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25401 — 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-25401 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