dbcve.org
AndroidOperating system · Samsung

CVE-2024-20805

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 ZipCompressor 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 · high confidence

Path traversal vulnerability in Samsung MyFiles ZipCompressor allows local attackers to write arbitrary files to the filesystem via specially crafted zip entries with traversal sequences (e.g., ../../../'). The vulnerability affects MyFiles prior to SMR Jan-2024 Release 1 on Android 11/12 and version 14.5.00.21 on Android 13.

MitigationApply vendor patch (SMR Jan-2024 Release 1 for Android 11/12, or version 14.5.00.21+ for Android 13) to remediate the path traversal in ZipCompressor. As a defense-in-depth measure, ensure proper input validation and path sanitization are implemented before file extraction.

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. Check Android version
    Go to Settings > About Phone > Android version, or run `getprop ro.build.version.release` via ADB
    Affected if Android version is 11.0 or 12.0 and MyFiles has not received SMR Jan-2024 Release 1 patch, or Android version is 13 with MyFiles version below 14.5.00.21
  2. Locate MyFiles app version
    Open Galaxy Store > Menu > My apps > MyFiles, or go to Settings > Apps > MyFiles > App info, or check package version via ADB: `dumpsys package com.sec.android.app.myfiles`
    Affected if Version displayed is below 14.5.00.21 on Android 13, or version is unknown/older on Android 11/12 without SMR Jan-2024 update
  3. Verify ZipCompressor component
    The ZipCompressor module is bundled within MyFiles. Attempt to extract a known safe zip file via MyFiles > three-dot menu > Zip, or inspect the app components via `dumpsys package com.sec.android.app.myfiles` and look for compressor-related activities
    Affected if MyFiles is present and functional - the path traversal applies when extracting zip files containing "../" sequences

User is affected if running Android 11 or 12 without the SMR Jan-2024 patch, or Android 13 with MyFiles version below 14.5.00.21, and they use MyFiles ZipCompressor to extract zip files from untrusted sources.

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

Apply vendor patch (SMR Jan-2024 Release 1 for Android 11/12, or version 14.5.00.21+ for Android 13) to remediate the path traversal in ZipCompressor. As a defense-in-depth measure, ensure proper input validation and path sanitization are implemented before file extraction.

Recommended fix High confidence

SMR Jan-2024 Release 1 (MyFiles version 14.5.00.21 for Android 13)

  1. 1. Open Settings on the Samsung device
  2. 2. Navigate to Apps > MyFiles (or Apps > Files)
  3. 3. Check the current version of MyFiles under App info
  4. 4. Ensure the device has the latest Samsung security update installed via Settings > Software update > Download and install
  5. 5. For Android 11/12: Update to SMR Jan-2024 Release 1 or later which includes the fixed MyFiles version
  6. 6. For Android 13: Update to MyFiles version 14.5.00.21 or later
  7. 7. Alternatively, verify patch level is January 2024 SMR or later in Settings > About phone > Software information > Security patch level

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

Fix this in Android 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-2024-20805 — 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-20805 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