CVE-2020-1836
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 P30 with versions earlier than 10.1.0.160(C00E160R2P11) and HUAWEI P30 Pro with versions earlier than 10.1.0.160(C00E160R2P8) have an information disclosure vulnerability. Certain function's default configuration in the system seems insecure, an attacker should craft a WI-FI hotspot to launch the attack. Successful exploit could cause information disclosure.
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 confidenceInformation disclosure vulnerability in HUAWEI P30 and P30 Pro devices stemming from insecure default configuration in a certain system function. The attack requires the victim to connect to a malicious Wi-Fi hotspot crafted by the attacker, potentially exposing sensitive information through this attack vector.
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< 10.1.0.160\(c00e160r2p11\)< 10.1.0.160\(c00e160r2p8\)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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/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.
-
Check device firmware version on Huawei P30Navigate to Settings > About Phone > Version on the Huawei P30 device. Record the build number displayed (e.g., 10.1.0.XXX(c00e160r2pXX)).Affected if The version is below 10.1.0.160(c00e160r2p11)
-
Check device firmware version on Huawei P30 ProNavigate to Settings > About Phone > Version on the Huawei P30 Pro device. Record the build number displayed (e.g., 10.1.0.XXX(c00e160r2pXX)).Affected if The version is below 10.1.0.160(c00e160r2p8)
-
Determine if Wi-Fi connectivity is enabledCheck if Wi-Fi is turned on in the device settings (Settings > Network & Internet > Wi-Fi) or by observing the Wi-Fi icon in the status bar.Affected if Wi-Fi is enabled and the device is running a firmware version below the patched releases, making it susceptible to the malicious hotspot attack vector
The device is affected if it is a Huawei P30 running firmware below 10.1.0.160(c00e160r2p11) or a Huawei P30 Pro running firmware below 10.1.0.160(c00e160r2p8), and Wi-Fi connectivity is available.
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 data10.1.0.160
Update affected devices (P30 before 10.1.0.160(C00E160R2P11), P30 Pro before 10.1.0.160(C00E160R2P8)) to the patched version to remediate the insecure default configuration.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1836 — 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-2020-1836 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