CVE-2017-2733
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 · uneditedHonor 6X smartphones with software versions earlier than BLN-AL10C00B357 and versions earlier than BLN-AL20C00B357 have an information leak vulnerability due to improper file permission configuration. An attacker tricks a user into installing a malicious application on the smart phone, and the application can get the file that keep the cipher text of the SIM card PIN.
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 confidenceHonor 6X smartphones with versions earlier than BLN-AL10C00B357 and BLN-AL20C00B357 contain an information disclosure vulnerability where improper file permission configuration allows a malicious application installed on the device to access a file containing the encrypted SIM card PIN cipher text.
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< bln-al10c00b357< bln-al20c00b357CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 your Honor 6X model numberGo to Settings > About Phone and note the model number - look for BLN-AL10 or BLN-AL20Affected if Your model is BLN-AL10 or BLN-AL20 (other models are not affected by this CVE)
-
Check your current firmware versionGo to Settings > About Phone > Version and record the build number shownAffected if The firmware version is visible on the screen - you need to compare this to the affected ranges
-
Compare BLN-AL10 firmware to affected rangeIf your model is BLN-AL10, compare your build number against BLN-AL10C00B357 - check if it is earlier than (less than) this versionAffected if Your version is earlier than BLN-AL10C00B357 (e.g., BLN-AL10C00B340 or similar)
-
Compare BLN-AL20 firmware to affected rangeIf your model is BLN-AL20, compare your build number against BLN-AL20C00B357 - check if it is earlier than (less than) this versionAffected if Your version is earlier than BLN-AL20C00B357 (e.g., BLN-AL20C00B340 or similar)
-
Confirm the file permission vulnerability contextThis CVE relates to improper file permissions on a system file that stores encrypted SIM PIN data - the vulnerability exists if your firmware version is below the thresholds regardless of other factorsAffected if Your firmware version is below the indicated threshold for your specific model
You are affected if you have an Honor 6X (BLN-AL10 or BLN-AL20) with firmware version earlier than BLN-AL10C00B357 (for BLN-AL10) or BLN-AL20C00B357 (for BLN-AL20).
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 dataUpdate Honor 6X firmware to version BLN-AL10C00B357 or later (for BLN-AL10 model) and BLN-AL20C00B357 or later (for BLN-AL20 model) to remediate the improper file permission configuration.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2733 — 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-2733 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