dbcve.org
Mate 30 FirmwareOperating system · Huawei

CVE-2020-1839

MEDIUM · 6.3 CVSS v3.1 Published 2020-07-06
Fix available
A fix is available. Upgrade to 10.1.0.150 or later.
See remediation →
63/100
Remediation priority · Elevated

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 Mate 30 with versions earlier than 10.1.0.150(C00E136R5P3) have a race condition vulnerability. There is a timing window exists in which certain pointer members can be modified by another process that is operating concurrently, an attacker should trick the user into running a crafted application with high privilege, successful exploit could cause code execution.

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 confidence

A race condition vulnerability in HUAWEI Mate 30 firmware versions earlier than 10.1.0.150(C00E136R5P3) creates a timing window where concurrent processes can modify pointer members. Successful exploitation requires tricking a user into running a crafted high-privilege application, which can then lead to arbitrary code execution.

MitigationApply the vendor firmware update (version 10.1.0.150(C00E136R5P3) or later) to patch the race condition vulnerability.

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
Mate 30 FirmwareOperating system
Affected:< 10.1.0.150\(c00e136r5p3\)

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
Local
Complexity
High
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H

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. Confirm device model is Huawei Mate 30
    Check the device settings or system information to verify the exact model number of the phone
    Affected if Device is any model other than Huawei Mate 30 - the vulnerability only affects Mate 30
  2. Check installed firmware version
    Navigate to Settings > About Phone > Version on the device, or use *#*#2846579#*#* to access engineering menu, or check via Huawei HiSuite PC software
    Affected if Firmware version cannot be determined or is earlier than 10.1.0.150(C00E136R5P3)
  3. Verify firmware build number
    Look for the specific build identifier (C00E136R5P3) in the version details - the full version string typically appears as 10.1.0.150(C00E136R5P3)
    Affected if Build number is missing, shows a different build, or is earlier than C00E136R5P3

The device is affected if it is a Huawei Mate 30 running firmware version earlier than 10.1.0.150(C00E136R5P3); devices on version 10.1.0.150(C00E136R5P3) or later, or non-Mate 30 devices, are not affected by this specific CVE.

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.150 or later
Fixed in 10.1.0.150
Interim mitigation

Apply the vendor firmware update (version 10.1.0.150(C00E136R5P3) or later) to patch the race condition vulnerability.

Fix this in Mate 30 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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