dbcve.org
P30 FirmwareOperating system · Huawei

CVE-2019-5265

HIGH · 7.5 CVSS v3.1 Published 2019-12-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable 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 Share function in P30 9.1.0.193(C00E190R2P1) smartphone has an improper access control vulnerability. The function incorrectly controls certain access messages, attackers can simulate a sender to steal P2P network information. Successful exploit may cause information leakage.

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 Huawei Share function in P30 smartphones (version 9.1.0.193) contains an improper access control vulnerability. Attackers can simulate a legitimate sender to intercept P2P network information, enabling unauthorized access to sensitive data being shared between devices.

MitigationApply the Huawei firmware update (C00E190R2P1 or later) to patch the access control flaw. Until patched, avoid using Huawei Share in untrusted environments to prevent P2P network information leakage.

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:= 9.1.0.193\(c00e190r2p1\)

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/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. Check the installed firmware version on the Huawei P30
    Go to Settings > About Phone > Version, or use *#*#2846579#*#* to access the engineering menu, and look for the build number (C00E190R2P1)
    Affected if The firmware version displayed is 9.1.0.193 (C00E190R2P1)
  2. Verify the exact software version string
    In Settings > About Phone > Version, confirm the full version number reads exactly 9.1.0.193(c00e190r2p1)
    Affected if The version string matches 9.1.0.193 with build code c00e190r2p1 exactly
  3. Confirm Huawei Share feature is enabled
    Go to Settings > Device Connectivity > Huawei Share (or Settings > Connections > Huawei Share), and check if the toggle is turned ON
    Affected if Huawei Share is currently enabled on the device

The device is affected if it runs firmware version 9.1.0.193 (c00e190r2p1) AND has Huawei Share enabled, allowing attackers on the same P2P network to intercept shared data.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Huawei firmware update (C00E190R2P1 or later) to patch the access control flaw. Until patched, avoid using Huawei Share in untrusted environments to prevent P2P network information leakage.

Fix this in P30 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5265 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2019-5265 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