CVE-2017-2699
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 Huawei Themes APP in versions earlier than PLK-UL00C17B385, versions earlier than CRR-L09C432B380, versions earlier than LYO-L21C577B128 has a privilege elevation vulnerability. An attacker could exploit this vulnerability to upload theme packs containing malicious files and trick users into installing the theme packets, resulting in the execution of arbitrary code.
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 confidenceA privilege elevation vulnerability in the Huawei Themes APP allows attackers to embed malicious files within theme packs and trick users into installing them, resulting in arbitrary code execution. The vulnerability stems from insufficient validation of theme pack contents during the installation process, enabling code to execute with elevated privileges.
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< plk-ul00c17b385< crr-l09c432b380< lyo-l21c577b128CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.
-
Identify your device modelGo to Settings > About Phone and note the exact model name (such as Honor 7, Mate S, or Lyo L21)Affected if The device is a Huawei Honor 7, Mate S, or Lyo L21 model
-
Check your current firmware versionNavigate to Settings > About Phone > Version and record the build number or firmware version stringAffected if The firmware version is earlier than plk-ul00c17b385 (for Honor 7), crr-l09c432b380 (for Mate S), or lyo-l21c577b128 (for Lyo L21)
-
Verify the Huawei Themes APP is installedCheck your app drawer or go to Settings > Apps for the 'Themes' or 'Huawei Themes' applicationAffected if The Themes application is present on the device
-
Compare your firmware version to affected rangesCompare your recorded firmware version against the vulnerable versions: for PLK-UL00 devices below plk-ul00c17b385, CRR-L09 devices below crr-l09c432b380, and LYO-L21 devices below lyo-l21c577b128Affected if Your firmware version falls within any of these vulnerable version ranges
-
Review recently installed theme packsCheck the Themes app history or your download folder for any theme packs installed from untrusted or unknown sourcesAffected if Theme packs from untrusted sources have been installed on the device
You are affected if you own a Huawei Honor 7, Mate S, or Lyo L21 device running firmware version below the specified thresholds (plk-ul00c17b385, crr-l09c432b380, or lyo-l21c577b128 respectively) and have the Themes app installed with potentially untrusted theme packs.
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 the Huawei Themes APP to version PLK-UL00C17B385 or later for PLK-UL00, CRR-L09C432B380 or later for CRR-L09, and LYO-L21C577B128 or later for LYO-L21 devices. Until updated, users should avoid installing theme packs from untrusted sources.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2699 — 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-2699 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