CVE-2024-57960
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 · uneditedInput verification vulnerability in the ExternalStorageProvider module Impact: Successful exploitation of this vulnerability may affect service confidentiality.
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 confidenceInput verification vulnerability in Android's ExternalStorageProvider module allows attackers to potentially access sensitive files outside intended storage boundaries. The flaw permits improper validation of external storage access requests, leading to unauthorized disclosure of confidential data.
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= 13.0.0= 14.0.0= 3.0.0= 3.1.0= 4.0.0= 4.2.0= 4.3.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device OS versionNavigate to Settings > About Phone on the Huawei device and record the EMUI or HarmonyOS version number displayedAffected if The version matches exactly 13.0.0 or 14.0.0 for EMUI, or 3.0.0, 3.1.0, 4.0.0, 4.2.0, or 4.3.0 for HarmonyOS
-
Verify ExternalStorageProvider module presenceCheck system app information for the ExternalStorageProvider or Storage provider component through Settings > Apps > Show system apps, or use adb shell dumpsys package to list providersAffected if The ExternalStorageProvider component is present and enabled on the device
-
Review external storage permissionsInspect app permissions via Settings > Privacy > Permission Manager > Storage and verify which applications have broad external storage accessAffected if Applications are granted READ_EXTERNAL_STORAGE or WRITE_EXTERNAL_STORAGE permissions without explicit need
-
Examine file access audit logsCheck system logs (logcat) or security audit logs for unusual access patterns to directories outside the typical /sdcard/ scope, such as unexpected access to /data/ or /storage/emulated/0/ subdirectoriesAffected if Logs show file access attempts to paths outside the standard external storage sandbox boundaries
The device is affected if it runs EMUI 13.0.0/14.0.0 or HarmonyOS 3.0.0/3.1.0/4.0.0/4.2.0/4.3.0 and has the ExternalStorageProvider module enabled with external storage permissions configured.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply available Android security patches addressing input validation in ExternalStorageProvider; restrict external storage permissions and monitor for unauthorized file access attempts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-57960 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-57960 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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