CVE-2021-25506
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 · uneditedNon-existent provider in Samsung Health prior to 6.19.1.0001 allows attacker to access it via malicious content provider or lead to denial of service.
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 confidenceSamsung Health prior to version 6.19.1.0001 contains a content provider component that references a non-existent provider. A malicious application can exploit this by registering a content provider with the same name, potentially causing a denial of service or accessing unintended app functionality.
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.19.1.0001CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 installed Samsung Health versionOpen device Settings > Apps > Samsung Health, then view the Version information listed under App info, or use ADB command: `adb shell dumpsys package com.sec.android.app.shealth` and locate the versionName in the outputAffected if The displayed version is earlier than 6.19.1.0001
-
Identify the vulnerable content provider authorityExtract the Samsung Health APK and inspect the AndroidManifest.xml file for <provider> elements. Look for a content provider with an authority string that references a non-existent provider componentAffected if A content provider declaration exists in the manifest that points to a provider class that is not implemented within the app
-
Check for conflicting content provider registrationUse ADB command: `adb shell dumpsys package | grep -A 5 "ContentProvider"` to list all registered content providers on the device. Search for any provider authority matching the one declared in Samsung Health but owned by a different packageAffected if A content provider with the same authority string as Samsung Health's vulnerable provider is registered by another application
-
Verify provider permission configurationReview the AndroidManifest.xml of Samsung Health and check the android:permission attribute on the vulnerable <provider> element to determine if permission checks are properly enforcedAffected if The content provider lacks a android:permission attribute or has weak permission settings allowing unauthorized access
You are affected if Samsung Health version is earlier than 6.19.1.0001 and the vulnerable content provider with misconfigured authority is present in your installation.
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 · scoped6.19.1.0001
Update Samsung Health to version 6.19.1.0001 or later. As a defense-in-depth measure, implement strict provider permission checks and validate all inter-app communications.
6.19.1.0001
- Open Google Play Store or Samsung Galaxy Store on the device
- Search for 'Samsung Health'
- Tap 'Update' to install version 6.19.1.0001 or later
- Alternatively, go to Settings > Apps > Samsung Health and check for updates through the app store
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25506 — 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-25506 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