dbcve.org
AndroidOperating system · Samsung

CVE-2024-34654

MEDIUM · 5.5 CVSS v3.1 Published 2024-09-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Export of android application component in My Files prior to SMR Sep-2024 Release 1 allows local attackers to access files with My Files' 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 · high confidence

The My Files application on Samsung devices has an improperly exported Android component (likely an Activity or Content Provider) that allows any locally installed application to access it without proper authorization. This enables a malicious app to invoke the exported component and read files that My Files has permission to access, achieving privilege escalation through the app's elevated file system privileges.

MitigationApply the SMR Sep-2024 Release 1 or later security update to patch the improperly exported component. If unable to update, verify that the component is explicitly set to android:exported="false" in the AndroidManifest.xml.

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
AndroidOperating system
Affected:= 13.0= 14.0

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. Confirm your Samsung device is running Android 13.0 or 14.0
    Go to Settings > About Phone > Android version and verify the version number displays either 13.0 or 14.0
    Affected if Your device runs Android 13.0 or 14.0 and has not received the Sep-2024 security update
  2. Verify the Samsung My Files app is installed
    Locate the My Files application in your app drawer or go to Settings > Apps > My Files to confirm it is present
    Affected if The My Files application is installed on your device
  3. Check your devices security patch level
    Go to Settings > About Phone > Software info > Security patch level and verify the date. The patch should be September 2024 or later (SMR Sep-2024 Release 1 or later)
    Affected if The security patch level is earlier than September 2024 (the vulnerability remains unpatched)
  4. Inspect My Files app manifest for exported components (requires ADB or root)
    Using ADB, run: adb shell pm dump <package_name> | grep -A 10 'android:exported' where package_name is the Samsung My Files package (typically com.sec.android.app.myfiles). Look for any Activity or ContentProvider with android:exported="true" that should not be accessible
    Affected if A component that handles file access is exported without proper authorization (android:exported="true" without android:permission)

Your device is affected if it is a Samsung running Android 13.0 or 14.0, has the My Files app installed, and has not received the September 2024 or later security update (or the component remains exported in the manifest).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the SMR Sep-2024 Release 1 or later security update to patch the improperly exported component. If unable to update, verify that the component is explicitly set to android:exported="false" in the AndroidManifest.xml.

Recommended fix High confidence

Samsung My Files with SMR Sep-2024 Release 1 (September 2024 Android Security Patch)

  1. Navigate to Settings > Software update on your Samsung Android device
  2. Tap 'Download and install' to check for the latest security updates
  3. Ensure the device updates to the September 2024 security patch level (SMR Sep-2024 Release 1)
  4. After updating, verify the My Files application has been updated with the security fix
Caveat Standard security update; no breaking changes expected for My Files functionality

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

Fix this in Android Scoped from the published advisory
  • Consultation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34654 — 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-2024-34654 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