CVE-2018-7930
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 Near Field Communication (NFC) module in Mate 9 Huawei mobile phones with the versions before MHA-L29B 8.0.0.366(C567) has an information leak vulnerability due to insufficient validation on data transfer requests. When an affected mobile phone sends files to an attacker's mobile phone using the NFC function, the attacker can obtain arbitrary files from the mobile phone, causing information leaks.
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 confidenceThe NFC module in Huawei Mate 9 phones before version MHA-L29B 8.0.0.366(C567) lacks proper validation on data transfer requests. When a user initiates an NFC file transfer to another device, an attacker can exploit insufficient bounds checking to read arbitrary files from the victim's phone beyond the intended transfer contents.
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< mha-l29b_8.0.0.366\(c567\)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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:A/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.
-
Confirm device model is Huawei Mate 9Check the phone settings under Settings > About Phone to verify the model number is Huawei Mate 9 or variant (e.g., MHA-L29)Affected if The device is not a Huawei Mate 9 model - different models are not affected by this specific CVE
-
Check installed firmware versionNavigate to Settings > About Phone > Version and locate the build number or firmware version string (typically looks like mha-l29b_8.x.x.xxx or similar)Affected if The firmware version is lower than mha-l29b_8.0.0.366(C567) - versions at or above this threshold are patched
-
Verify NFC is enabled on the deviceGo to Settings > NFC (or Settings > Connections > NFC) to check if NFC functionality is turned onAffected if NFC is enabled - the vulnerability exists within the NFC module, so it must be active for exploitation to be possible
-
Identify if NFC file transfer feature is usedObserve whether the device is configured to use Android Beam or NFC-based file sharing for transferring files to other devicesAffected if The device uses NFC to transfer files - the flaw is exploited during NFC file transfer operations, specifically when sending files to another device
The user is affected if they own a Huawei Mate 9 with firmware version below mha-l29b_8.0.0.366(C567) and actively use NFC file transfer functionality.
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 the vendor firmware update MHA-L29B 8.0.0.366(C567) or later to patch the NFC validation vulnerability. Until updated, avoid using NFC to transfer files to untrusted devices.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7930 — 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-7930 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