CVE-2020-1803
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 smartphones Honor V20 with versions earlier than 10.0.0.179(C636E3R4P3),versions earlier than 10.0.0.180(C185E3R3P3),versions earlier than 10.0.0.180(C432E10R3P4) have an information disclosure vulnerability. The device does not sufficiently validate the identity of smart wearable device in certain specific scenario, the attacker need to gain certain information in the victim's smartphone 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 confidenceThe Honor V20 smartphone has an information disclosure vulnerability where the device does not sufficiently validate the identity of connected smart wearable devices. An attacker who has already obtained certain information from the victim's smartphone could exploit this improper validation to disclose additional sensitive information.
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.0.0.179\(c636e3r4p3\)< 10.0.0.180\(c185e3r3p3\)< 10.0.0.180\(c432e10r3p4\)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.
-
Confirm device model is Honor V20Navigate to Settings > About Phone > Model Name, or check the physical device labelAffected if Model name is not Honor V20 (then not affected by this specific CVE)
-
Check firmware build number C636E3R4P3Navigate to Settings > About Phone > Version > Build Number, or dial *#*#2846579#*#* to access service menu, or run 'adb shell getprop ro.build.version.emui'Affected if Build number is less than C636E3R4P3 (for that branch)
-
Check firmware build number C185E3R3P3Navigate to Settings > About Phone > Version > Build Number, or run 'adb shell getprop ro.build.version.emui'Affected if Build number is less than C185E3R3P3 (for that branch)
-
Check firmware build number C432E10R3P4Navigate to Settings > About Phone > Version > Build Number, or run 'adb shell getprop ro.build.version.emui'Affected if Build number is less than C432E10R3P4 (for that branch)
-
Identify the active firmware branchLook at the full build number string (for example: C636E3R4P3) - the letter before the three-digit number indicates the region/branchAffected if Any branch version is below its respective patched version
The device is affected if it is an Honor V20 running firmware version lower than 10.0.0.179(C636E3R4P3), 10.0.0.180(C185E3R3P3), or 10.0.0.180(C432E10R3P4) depending on which firmware branch is installed.
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.0.0.17910.0.0.180
Users should update their Honor V20 to version 10.0.0.179(C636E3R4P3), 10.0.0.180(C185E3R3P3), or 10.0.0.180(C432E10R3P4) or later to patch the vulnerability. Until updated, limit pairing with untrusted wearable devices.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1803 — 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-1803 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