P30 FirmwareOperating system · Huawei

CVE-2020-9260

MEDIUM · 6.5 CVSS v3.1 Published 2020-07-10
Fix available
A fix is available. Upgrade to 10.1.0.123 / 10.1.0.160 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
HUAWEI P30 and HUAWEI P30 Pro smartphones with versions earlier than 10.1.0.123(C432E22R2P5) and versions earlier than 10.1.0.160(C00E160R2P8) have an information disclosure vulnerability. Certain WI-FI 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 · high confidence

The vulnerability exists in the default Wi-Fi configuration on Huawei P30 and P30 Pro smartphones. An attacker can set up a malicious Wi-Fi hotspot to exploit insecure default settings in the Wi-Fi function, leading to information disclosure.

MitigationUpdate the device firmware to version 10.1.0.123(C432E22R2P5) or 10.1.0.160(C00E160R2P8) or later to patch the insecure default Wi-Fi configuration.

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
P30 FirmwareOperating system
Affected:< 10.1.0.123\(c432e22r2p5\)
P30 Pro FirmwareOperating system
Affected:< 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your device model
    Go to Settings > About Phone and verify the model is either Huawei P30 or Huawei P30 Pro
    Affected if Device model is Huawei P30 or P30 Pro
  2. Check the firmware build number
    Navigate to Settings > About Phone > Build Number and note the full build string displayed
    Affected if For P30: build number is lower than 10.1.0.123(c432e22r2p5); For P30 Pro: build number is lower than 10.1.0.160(c00e160r2p8)
  3. Verify the EMUI version
    Go to Settings > About Phone > EMUI Version to confirm the exact software version
    Affected if EMUI version corresponds to a build earlier than the patched releases specified above

You are affected if you have a Huawei P30 or P30 Pro running firmware below version 10.1.0.123(c432e22r2p5) or 10.1.0.160(c00e160r2p8) respectively.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 10.1.0.123 / 10.1.0.160 or later
Fixed in 10.1.0.12310.1.0.160
Interim mitigation

Update the device firmware to version 10.1.0.123(C432E22R2P5) or 10.1.0.160(C00E160R2P8) or later to patch the insecure default Wi-Fi configuration.

Fix this in P30 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-9260 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-9260 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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