CVE-2017-17324
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 · uneditedHuawei Mate 9 Pro smartphones with software LON-AL00BC00B139D; LON-AL00BC00B229 have an integer overflow vulnerability. The camera driver does not validate the external input parameters and causes an integer overflow, which in the after processing results in a buffer overflow. An attacker tricks the user to install a crafted application, successful exploit could cause malicious 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 confidenceInteger overflow vulnerability in the camera driver of Huawei Mate 9 Pro (versions LON-AL00BC00B139D and LON-AL00BC00B229). The driver fails to validate external input parameters, causing an integer overflow during processing that leads to buffer overflow. An attacker tricks the user into installing a crafted malicious application to trigger the vulnerability, potentially achieving arbitrary code execution.
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= lon-al00bc00b139d= lon-al00bc00b229CVSS 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 modelGo to Settings > About Phone > Model Number, or run 'getprop ro.product.model' via ADB shellAffected if Device is not Huawei Mate 9 Pro (vulnerability only affects this specific model)
-
Check firmware versionGo to Settings > About Phone > Build Number, or run 'getprop ro.build.display.id' via ADB shellAffected if Firmware version equals 'LON-AL00BC00B139D' or 'LON-AL00BC00B229' exactly
-
Verify camera driver is accessibleCheck if camera app can be opened and accessed, or verify camera driver module exists via 'ls /dev/video*' or 'getprop video.driver.version' in ADB shellAffected if Camera functionality is available and accessible on the device (the vulnerable driver must be present)
-
Confirm application installation capabilityVerify whether the device allows installing applications from unknown sources (Settings > Security > Unknown Sources)Affected if Device permits installing apps from untrusted sources, which is required for the attack vector described
The device is affected if it is a Huawei Mate 9 Pro with firmware version LON-AL00BC00B139D or LON-AL00BC00B229, and the camera driver is accessible and applications can be installed from untrusted sources.
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 vendor-supplied firmware/security patch to update the device to a patched software version. Users should avoid installing applications from untrusted sources to reduce attack surface.
- Consultation6.0 h
- Implementation10.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17324 — 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-17324 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