HealthApplication · Samsung

CVE-2023-30723

CRITICAL · 9.8 CVSS v3.1 Published 2023-09-06
Fix available
A fix is available. Upgrade to 6.24.2.011 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 input validation vulnerability in Samsung Health prior to version 6.24.2.011 allows attackers to write arbitrary file with Samsung Health privilege.

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 confidence

Improper input validation vulnerability in Samsung Health app versions prior to 6.24.2.011 allows attackers to write arbitrary files to the filesystem using the application's elevated privileges. This critical vulnerability (CVSS 9.8) stems from insufficient validation of user-controlled input paths, enabling path traversal or similar attacks to place files outside intended directories.

MitigationUpdate Samsung Health to version 6.24.2.011 or later via the Galaxy Store or Google Play Store. Organizations should verify endpoint detection and consider mobile device management policies to ensure all managed devices have the updated application.

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.2.011

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Verify Samsung Health is installed
    On the Android device, go to Settings > Apps and search for Samsung Health, or use ADB command: 'adb shell pm list packages | grep com.sec.android.app.shealth'
    Affected if The package com.sec.android.app.shealth exists on the device
  2. Retrieve the installed version number
    In Settings > Apps > Samsung Health > App info, note the Version number displayed; alternatively use ADB: 'adb shell dumpsys package com.sec.android.app.shealth | grep versionName'
    Affected if A version number is returned showing the installed build
  3. Compare version against the affected range
    Compare the installed version (e.g., 6.24.0.000, 6.23.5.015) to the fixed version 6.24.2.011 - any version below 6.24.2.011 is affected
    Affected if The installed version is lower than 6.24.2.011 (for example, 6.24.1.x, 6.23.x, or earlier)
  4. Confirm the vulnerability is exploitable
    The flaw requires the app to process user-supplied file paths through the vulnerable input validation - this occurs during normal app operations involving file imports or data synchronization features
    Affected if The app is actively used and processes external input, enabling path traversal attacks to write files outside intended directories

A device is affected if Samsung Health is installed with any version lower than 6.24.2.011, as the improper input validation vulnerability exists in those versions and can be triggered during app usage.

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.2.011 or later
Fixed in 6.24.2.011
Interim mitigation

Update Samsung Health to version 6.24.2.011 or later via the Galaxy Store or Google Play Store. Organizations should verify endpoint detection and consider mobile device management policies to ensure all managed devices have the updated application.

Recommended fix High confidence

6.24.2.011 or later

  1. Open the Galaxy Store or Google Play Store on your Samsung device
  2. Search for 'Samsung Health'
  3. Update Samsung Health to version 6.24.2.011 or later
  4. Verify the update was successful by checking the app version in Samsung Health settings

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

Fix this in Health Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30723 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30723 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