CVE-2017-2715
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 · uneditedThe Files APP 7.1.1.309 and earlier versions in some Huawei mobile phones has a brute-force password cracking vulnerability due to the improper design of the Safe key database. An unauthorized attacker could access sensitive database information and may crack users' Safe passwords, leading to information leak.
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 confidenceThe Files APP 7.1.1.309 and earlier on Huawei mobile phones contains a brute-force vulnerability in its Safe key database due to improper cryptographic design. The Safe feature (used to secure sensitive files) stores passwords in a way that allows attackers to easily crack user passwords by brute-force methods, leading to unauthorized access to 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<= 7.1.1.309CVSS 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
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Confirm Huawei Files app is installedCheck your device's installed applications for 'Files' or 'Files by Huawei' (com.huawei.filemanager or similar package name)Affected if The app is not present on the device, the vulnerability does not apply
-
Identify the installed version of Huawei FilesNavigate to Settings > Apps > Files > Version info, or use 'adb shell dumpsys package com.huawei.filemanager' to retrieve the versionName and versionCodeAffected if The installed version is 7.1.1.309 or earlier
-
Determine if Safe feature has been usedLook for the Safe key database file, typically located at /data/data/com.huawei.filemanager/databases/safe_key.db or similar path under the app's private data directory. On a non-rooted device, check if the Safe feature prompts for a password when accessing protected files.Affected if The Safe feature has been configured and contains protected files, meaning the weak cryptographic storage is actively in use
-
Verify the password storage mechanismIf you have root access, examine the safe_key.db file using sqlite3 to inspect the password hash storage method. Check if the cryptographic implementation uses weak hashing (such as MD5 or SHA1 without salt) instead of proper password hashing algorithms like bcrypt or PBKDF2.Affected if The database shows the password is stored with weak hashing algorithms, confirming the vulnerability is exploitable
You are affected if Huawei Files app version 7.1.1.309 or earlier is installed AND you have configured or used the Safe feature to protect files, as the weak cryptographic storage allows brute-force password cracking.
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 dataUpgrade the Files APP to a patched version that implements proper password hashing and cryptographic storage for the Safe key database. If patching is unavailable, advise users to avoid storing highly sensitive data in the Safe feature.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2715 — 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-2017-2715 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