dbcve.org
AndroidOperating system · Samsung

CVE-2024-20804

MEDIUM · 5.5 CVSS v3.1 Published 2024-01-04
Fix available
A fix is available. Upgrade to 14.5.00.21 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
Path traversal vulnerability in FileUriConverter of MyFiles prior to SMR Jan-2024 Release 1 in Android 11 and Android 12, and version 14.5.00.21 in Android 13 allows local attackers to write arbitrary file.

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

A path traversal vulnerability exists in the FileUriConverter component of Samsung's MyFiles application on Android 11, 12, and 13. The vulnerability allows local attackers to write files to arbitrary locations on the device filesystem by manipulating file paths in the converter.

MitigationUpdate MyFiles to SMR Jan-2024 Release 1 (Android 11/12) or version 14.5.00.21 (Android 13) to receive the patch. As a temporary mitigation, limit local device access and avoid using untrusted file management applications.

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:= 11.0= 12.0
MyfilesApplication
Affected:< 14.5.00.21

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
None
Integrity
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Android version is 11, 12, or 13
    Go to Settings > About Phone > Android version and note the displayed version number
    Affected if Android version shows 11.0, 12.0, or 13.x (any subversion)
  2. Confirm MyFiles application is installed
    Go to Settings > Apps > search for MyFiles or Samsung MyFiles application
    Affected if MyFiles app is present on the device
  3. Check MyFiles version number
    In Settings > Apps > MyFiles > App info, note the version shown (format may appear as 14.x.x.x or similar)
    Affected if Installed MyFiles version is lower than 14.5.00.21
  4. Verify FileUriConverter component is accessible
    The vulnerability resides in the FileUriConverter component used by MyFiles when handling file URIs; check if MyFiles has permission to access and convert file URIs (go to Settings > Apps > MyFiles > Permissions)
    Affected if MyFiles has storage/file access permissions AND version is below 14.5.00.21 on affected Android versions

Device is affected if running Android 11 or 12 (any build) or Android 13, and MyFiles version is below 14.5.00.21, with the app having file access permissions enabled.

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 14.5.00.21 or later
Fixed in 14.5.00.21
Interim mitigation

Update MyFiles to SMR Jan-2024 Release 1 (Android 11/12) or version 14.5.00.21 (Android 13) to receive the patch. As a temporary mitigation, limit local device access and avoid using untrusted file management applications.

Recommended fix High confidence

MyFiles version 14.5.00.21 (part of SMR Jan-2024 Release 1)

  1. 1. Go to Settings on your Samsung device running Android 11, 12, or 13
  2. 2. Navigate to Apps > MyFiles (or Files)
  3. 3. Tap on MyFiles and go to App info
  4. 4. Check the current version under App version
  5. 5. If version is below 14.5.00.21, open Galaxy Store or Samsung Galaxy Store
  6. 6. Search for MyFiles or Files and check for available updates
  7. 7. Update to version 14.5.00.21 or later (SMR Jan-2024 Release 1)
  8. 8. Alternatively, check for system software updates via Settings > Software update > Download and install to receive the bundled SMR Jan-2024 release which includes the patched MyFiles

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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