CVE-2018-7940
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 smart phones Mate 10 and Mate 10 Pro with earlier versions than 8.0.0.129(SP2C00) and earlier versions than 8.0.0.129(SP2C01) have an authentication bypass vulnerability. An attacker with high privilege obtains the smart phone and bypass the activation function by some specific operations.
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 confidenceHuawei Mate 10 and Mate 10 Pro smartphones contain an authentication bypass vulnerability in earlier firmware versions before 8.0.0.129. An attacker with high privileges and physical access to the device can bypass the activation function (likely Factory Reset Protection) through specific operations.
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< 8.0.0.129\(sp2c00\)< 8.0.0.129\(sp2c01\)CVSS 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
- Physical
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/AC:L/PR:H/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.
-
Identify your Huawei device modelGo to Settings > About Phone (or System > About Device) and check the Model name. Confirm it is a Huawei Mate 10 or Mate 10 Pro.Affected if The model is Huawei Mate 10 or Mate 10 Pro.
-
Check the installed firmware versionGo to Settings > About Phone > Version (or Version Number). Note the full firmware build number displayed (for example: 8.0.0.120).Affected if The firmware version shown is below 8.0.0.129.
-
Verify the specific build variantExamine the full version string to see if it contains 'SP2C00' or 'SP2C01' suffix (for example: 8.0.0.120(SP2C00)). Compare this suffix against the affected variant for your model.Affected if The build variant ends in a number lower than SP2C00 (for Mate 10) or SP2C01 (for Mate 10 Pro), or lacks this suffix entirely.
-
Confirm the device has not been updatedCheck Settings > System > About Device > Build number. If the device has been patched, the version will display 8.0.0.129 or higher with the correct SP2C00/SP2C01 suffix.Affected if The version remains below 8.0.0.129 with the relevant suffix, indicating the firmware update has not been applied.
You are affected if your Huawei Mate 10 or Mate 10 Pro runs firmware version lower than 8.0.0.129 with the SP2C00 or SP2C01 suffix respectively.
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 data8.0.0.129
Update Huawei Mate 10 to version 8.0.0.129(SP2C00) or later, and Mate 10 Pro to version 8.0.0.129(SP2C01) or later via official Huawei firmware updates.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7940 — 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-2018-7940 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