Information disclosure in Huawei Mate 9
Key facts
- Attack vector
- Adjacent network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA. Impact type from CWE-200.
Summary
The 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.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Huawei | Mate 9 | The versions before MHA-L29B 8.0.0.366(C567) | — | No fix listed | CNA |
- Mate 9 VendorHuawei Affected The versions before MHA-L29B 8.0.0.366(C567) Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2018-7930
- 2026-10-03 Alias added: GHSA-fx44-x6g3-42f2
References
More Huawei Mate 9 Firmware vulnerabilities
- TI-2017-11224 Memory corruption in Huawei Mate 10 CVSS 3.0HIGH 8.8
- TI-2017-11229 Double free in Huawei Mate 9 CVSS 3.0HIGH 7.8
- TI-2017-05717 Use after free in Huawei Mate 9, Mate 9 Pro CVSS 3.0HIGH 7.8
- TI-2017-01958 Memory corruption in Huawei Mate 9 CVSS 3.0HIGH 7.8
- TI-2017-01948 Path traversal in Huawei Mate 9 CVSS 3.0HIGH 7.1
- TI-2017-01949 Mate 9 smartphones with software MHA-AL00AC00B125 have a privilege escalation… CVSS 3.0HIGH 7.1
Sources
- CVE-2018-7930 · CVE Program
- CVE-2018-7930 · NVD
- FIRST EPSS
- GHSA-fx44-x6g3-42f2 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences