CVE-2017-8160
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 Madapt Driver of some Huawei smart phones with software Earlier than Vicky-AL00AC00B172 versions,Vicky-AL00CC768B122,Vicky-TL00AC01B167,Earlier than Victoria-AL00AC00B172 versions,Victoria-TL00AC00B123,Victoria-TL00AC01B167 has a use after free (UAF) vulnerability. An attacker can trick a user to install a malicious application which has a high privilege to exploit this vulnerability, Successful exploitation may cause arbitrary code execution.
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 confidenceUse-after-free vulnerability in the Madapt Driver of certain Huawei smartphone models (Vicky and Victoria series) enables a malicious application with high privileges to achieve arbitrary code execution. The flaw exists in driver memory management where freed memory is accessed after being released.
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< vicky-al00ac00b172= vicky-al00cc768b122= vicky-tl00ac01b167< victoria-al00ac00b172_= victoria-tl00ac00b123= victoria-tl00ac01b167CVSS 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 device modelCheck the device model number in system settings under 'About Phone' or by running 'getprop ro.product.name' or 'getprop ro.product.model' in ADB shellAffected if Device model is NOT one of: Vicky Al00a, Vicky Al00c, Vicky Tl00a, Victoria Al00a, or Victoria Tl00a (these are the only affected models)
-
Check Vicky firmware versionRun 'getprop ro.build.version.emui' or check the firmware build number in settings under 'About Phone > Build Number'Affected if For Vicky Al00a: firmware version is less than vicky-al00ac00b172; For Vicky Al00c: version equals vicky-al00cc768b122; For Vicky Tl00a: version equals vicky-tl00ac01b167
-
Check Victoria firmware versionRun 'getprop ro.build.version.emui' or check the firmware build number in settings under 'About Phone > Build Number'Affected if For Victoria Al00a: firmware version is less than victoria-al00ac00b172_; For Victoria Tl00a: version equals victoria-tl00ac00b123 OR equals victoria-tl00ac01b167
-
Verify Madapt driver presenceCheck for the presence of the Madapt driver module by running 'ls /system/lib/modules/*madapt*' or 'find /system -name *madapt*' in ADB shellAffected if The Madapt driver is present on the device (the driver is required for the vulnerability to be exploitable)
Device is affected if it is a Vicky or Victoria series model with a firmware version matching exactly the affected versions listed, and the Madapt driver is present on the device.
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 affected Huawei devices to the patched software versions (Vicky-AL00AC00B172 or later, Victoria-AL00AC00B172 or later) to remediate the vulnerability. Restrict installation of applications from untrusted sources to reduce exploitation risk.
- Consultation4.0 h
- Testing8.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 $4,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8160 — 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-8160 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