CVE-2020-1835
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 Mate 30 with versions earlier than 10.1.0.126(C00E125R5P3) have an information disclosure vulnerability. A logic judgment error occurs when the system handling Bluetooth connections, an attacker could craft as an authenticated Bluetooth peer 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 confidenceA logic judgment error exists in the Bluetooth connection handling code of HUAWEI Mate 30 smartphones running firmware versions earlier than 10.1.0.126(C00E125R5P3). An attacker who has already authenticated as a Bluetooth peer can exploit this flaw to access sensitive information that should not be accessible to them.
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.126\(c00e125r5p3\)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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Huawei Mate 30Go to Settings > About Phone and verify the Model number shows Mate 30 or HMA-AL00/HMA-L29Affected if Device is not a Huawei Mate 30 (different models are not affected)
-
Check firmware version numberGo to Settings > About Phone > Version. Record the Build number or Software version shown (example format: 10.1.0.120(C00E125R5P2))Affected if Unable to locate version information in the About Phone section
-
Compare version against CVE thresholdCompare your firmware version to 10.1.0.126(C00E125R5P3). If your version starts with 10.1.0 and the numeric portion after 10.1.0 is less than 126, or if the Build ID is earlier than C00E125R5P3, you are in the affected rangeAffected if Firmware version is earlier than 10.1.0.126(C00E125R5P3) (e.g., 10.1.0.100, 10.0.5.50, etc.)
-
Verify Bluetooth is enabledCheck if Bluetooth is turned on in Settings > Bluetooth, or that Bluetooth has been used/paired with any deviceAffected if Bluetooth is disabled (vulnerability requires active Bluetooth stack to be exploitable)
You are affected if you own a Huawei Mate 30 running firmware version lower than 10.1.0.126(C00E125R5P3) and have Bluetooth enabled or have previously paired Bluetooth devices.
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.126
Apply the vendor-supplied firmware update (version 10.1.0.126(C00E125R5P3 or later) to all affected HUAWEI Mate 30 devices. Until updated, limit Bluetooth pairing to trusted devices only.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.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 $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1835 — 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-1835 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