CVE-2020-1813
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 P30 smart phone with versions earlier than 10.1.0.135(C00E135R2P11) have an improper authentication vulnerability. Due to improper authentication of specific interface, in specific scenario attackers could access specific interface without authentication. Successful exploit could allow the attacker to perform unauthorized operations.
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 confidenceAuthentication bypass vulnerability in HUAWEI P30 smartphones running versions earlier than 10.1.0.135(C00E135R2P11). A specific interface lacks proper authentication checks under certain conditions, allowing unauthenticated attackers to access the interface and perform unauthorized operations.
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.135\(c00e135r2p11\)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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check your Huawei P30 firmware versionGo to Settings > System > About Phone on the device, or dial *#*#2846579#*#* to access the engineering menu, and locate the build number or software version fieldAffected if The displayed version is earlier than 10.1.0.135(C00E135R2P11)
-
Confirm the exact build identifierLocate the full build number in the About Phone section, which typically appears as a longer alphanumeric string containing the version and build identifierAffected if The build string contains a version lower than C00E135R2P11 or the complete version number is less than 10.1.0.135
-
Identify the device model preciselyVerify the device is specifically a Huawei P30 (not a P30 Pro, P30 Lite, or other variant) by checking the model number in Settings > System > About Phone > Model NumberAffected if The device model is Huawei P30 and the firmware version meets the affected criteria
-
Verify the vulnerability conditionCross-reference your confirmed firmware version against the affected range: any version before 10.1.0.135(C00E135R2P11) is considered vulnerableAffected if The device runs any firmware version earlier than 10.1.0.135(C00E135R2P11)
If the device is a Huawei P30 running firmware version earlier than 10.1.0.135(C00E135R2P11), the device is affected by this authentication bypass vulnerability.
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.135
Update HUAWEI P30 to version 10.1.0.135(C00E135R2P11) or later to remediate this vulnerability.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1813 — 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-1813 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