dbcve.org
AndroidOperating system · Samsung

CVE-2024-34679

HIGH · 7.1 CVSS v3.1 Published 2024-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/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
Incorrect default permissions in Crane prior to SMR Nov-2024 Release 1 allows local attackers to access files with phone 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

Incorrect default file permissions in Huawei Crane (prior to SMR Nov-2024 Release 1) allow local attackers to access sensitive files that should be protected with elevated 'phone' privileges. The vulnerability stems from overly permissive default settings on the filesystem, enabling local users to read or modify files they should not have access to.

MitigationApply the SMR Nov-2024 Release 1 patch or later to correct the default permission settings. Verify that sensitive files are protected with appropriate restrictive access controls.

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:= 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
High
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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 14.0
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Android version equals 14.0 exactly
  2. Check Security Maintenance Release (SMR) patch level
    Go to Settings > About Phone > Software information > Build number, or run 'getprop ro.build.version.sem_platform' via ADB shell
    Affected if SMR patch level is before November 2024 Release 1 (typically shown as a date like 'Nov-2024' or earlier)
  3. Identify sensitive files with elevated privilege requirements
    Search for files in /data or system partitions that should require 'phone' or root-level access. Common sensitive locations include /data/data/<package>, /data/system/passwd, or /data/user_de directories. Use 'ls -la' to inspect permissions.
    Affected if Sensitive files are readable or writable by non-privileged users or apps without elevated 'phone' privileges
  4. Audit filesystem permissions on sensitive directories
    Run 'ls -la /data/' and check if directories like /data/data, /data/user, or /data/system have overly permissive permissions (e.g., world-readable or other-writable)
    Affected if Directories that should require elevated privileges are accessible to standard users or apps
  5. Verify permission context for protected files
    Use 'ls -Z' or 'ls -l' to examine security context of sensitive files. Check if files meant for 'phone' domain are labeled with incorrect SELinux contexts or Unix permissions.
    Affected if Files intended to be protected with 'phone' privileges have permissive SELinux labels or weak Unix permissions (e.g., 644, 777)

A device is affected if it runs Android 14.0 with an SMR patch level before November 2024 Release 1 AND exhibits overly permissive file permissions on sensitive system or data directories.

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 Nov-2024 Release 1 patch or later to correct the default permission settings. Verify that sensitive files are protected with appropriate restrictive access controls.

Recommended fix High confidence

SMR Nov-2024 Release 1 for Android 14.0

  1. Open Galaxy Store or Google Play Store on the Samsung device
  2. Search for 'Crane' (Samsung's file manager application)
  3. Update the Crane app to the latest available version
  4. Alternatively, check for system software updates and install SMR Nov-2024 Release 1 for Android 14.0
  5. Verify the update was successfully applied

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 help mitigating

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-34679 — 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-34679 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