CVE-2023-30734
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 · uneditedImproper access control vulnerability in Samsung Health prior to version 6.24.3.007 allows attackers to access sensitive information via implicit 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 · moderate confidenceThis is an improper access control vulnerability in Samsung Health's Android application where the app uses implicit intents to transmit sensitive health data. Implicit intents in Android don't specify a target component, allowing any installed application to intercept them if they declare matching intent filters, potentially exposing sensitive health information to malicious apps.
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.24.3.007CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Samsung Health is installedOpen Android Settings > Apps > Apps and look for Samsung Health in the list of installed applications, or run 'adb shell pm list packages | grep samsung.health' via ADBAffected if Samsung Health application is present on the device
-
Find installed Samsung Health versionIn Android Settings, go to Apps > Samsung Health > App info and locate the Version or Version number field displayed under the app nameAffected if Unable to determine the version number from app metadata
-
Compare version against affected rangeCompare the installed version number to the affected version range: any version below 6.24.3.007 is vulnerableAffected if Installed version is less than 6.24.3.007 (for example, 6.24.2.001, 6.23.5.000, etc.)
A user is affected if Samsung Health is installed and the installed version is lower than 6.24.3.007, as this older version uses implicit intents that can be intercepted by other applications to access sensitive health data.
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.24.3.007
Update Samsung Health to version 6.24.3.007 or later, which addresses the improper access control by replacing vulnerable implicit intents with explicit intents or adding appropriate permission checks.
Samsung Health 6.24.3.007 or later
- Open Samsung Health app on your Android device
- Navigate to the Settings menu within the app
- Check for updates or go to the app version information
- Update Samsung Health to version 6.24.3.007 or later
- Alternatively, update through the Google Play Store by searching for Samsung Health and selecting the update option
Generated from the published advisory — verify against the referenced sources before acting.
- 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-2023-30734 — 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-2023-30734 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