dbcve.org
HealthApplication · Samsung

CVE-2023-30737

MEDIUM · 5.5 CVSS v3.1 Published 2023-10-04
Fix available
A fix is available. Upgrade to 6.24.3.007 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Improper 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 · high confidence

This is an improper access control vulnerability in Samsung Health for Android. The app uses implicit intents to transmit sensitive health data, which allows any application on the device to intercept this information without proper authorization. Attackers can exploit this by registering a broadcast receiver to capture the implicit intents containing sensitive personal health information.

MitigationUsers should update Samsung Health to version 6.24.3.007 or later, which implements explicit intents and proper access control checks to prevent unauthorized access to sensitive health data.

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
HealthApplication
Affected:< 6.24.3.007

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Samsung Health is installed
    Open Settings > Apps on the Android device and search for 'Samsung Health', or use ADB command: adb shell pm list packages | grep samsung.health
    Affected if Samsung Health package (com.sec.android.app.shealth) is present on the device
  2. Find the installed version number
    In Settings > Apps > Samsung Health, note the version shown under 'App info', or use ADB: adb shell dumpsys package com.sec.android.app.shealth | grep versionName
    Affected if Unable to retrieve version information from the device
  3. Compare version against affected range
    Check if the installed version is below 6.24.3.007. Compare version strings numerically - for example, 6.24.2.001 or 6.23.5.015 would be affected, while 6.24.3.007 or higher would not.
    Affected if Installed version is less than 6.24.3.007 (for example, 6.24.2.001, 6.23.5.015, or any 6.x.x.x version below 6.24.3.007)
  4. Confirm the app handles sensitive health data
    This check is implicit based on the CVE nature - Samsung Health by design processes sensitive personal health information (heart rate, steps, sleep, workout data, etc.). No manual verification needed if the app is in use.
    Affected if Samsung Health is actively used to track or store personal health metrics

A user is affected if Samsung Health is installed with a version lower than 6.24.3.007, as this version introduced explicit intent controls to prevent unauthorized apps from intercepting sensitive health data transmissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.24.3.007 or later
Fixed in 6.24.3.007
Interim mitigation

Users should update Samsung Health to version 6.24.3.007 or later, which implements explicit intents and proper access control checks to prevent unauthorized access to sensitive health data.

Recommended fix High confidence

Samsung Health version 6.24.3.007 or later

  1. Open the Galaxy Store app on your Samsung device
  2. Search for "Samsung Health" in the Galaxy Store
  3. Tap on Samsung Health in the search results
  4. Tap the "Update" button to install version 6.24.3.007 or later
  5. Alternatively, open Google Play Store, search for Samsung Health, and update if a newer version is available
  6. If automatic updates are enabled, the app should update automatically within 24-48 hours

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Health Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30737 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30737 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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