CVE-2020-9066
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 OxfordP-AN10B with versions earlier than 10.0.1.169(C00E166R4P1) have an improper authentication vulnerability. The Application doesn't perform proper authentication when user performs certain operations. An attacker can trick user into installing a malicious plug-in to exploit this vulnerability. Successful exploit could allow the attacker to bypass the authentication 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 confidenceThe Huawei OxfordP-AN10B smartphone has an improper authentication vulnerability where the application fails to perform proper authentication checks when users perform certain operations. Attackers can exploit this by tricking users into installing a malicious plug-plugin, allowing unauthorized operations to be performed without authentication.
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.1.169\(c00e166r4p1\)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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelCheck the device settings to confirm the model is Huawei OxfordP-AN10B. Go to Settings > About Phone to view the model number.Affected if The device model is not Huawei OxfordP-AN10B, then this specific CVE does not apply.
-
Check installed firmware versionNavigate to Settings > About Phone > Version on the Huawei OxfordP-AN10B smartphone to view the currently installed firmware build number.Affected if Unable to retrieve the firmware version from the device settings.
-
Compare version against affected rangeCompare the installed firmware version string (such as the build number or EMUI version) to 10.0.1.169(C00E166R4P1). The affected range is any version less than this build.Affected if The installed firmware version is earlier than 10.0.1.169(C00E166R4P1), meaning the version number is less than the patched build.
-
Assess plugin installation behaviorReview any recently installed plug-ins or applications on the device. Check if any plugins from untrusted or unknown sources have been installed, particularly outside of the official Huawei AppGallery.Affected if The device has plug-ins installed from untrusted sources, which combined with the vulnerable firmware version would allow exploitation.
The device is affected if it is a Huawei OxfordP-AN10B with firmware version earlier than 10.0.1.169(C00E166R4P1) and has plugins from untrusted sources 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.1.169
Update Huawei OxfordP-AN10B smartphones to version 10.0.1.169(C00E166R4P1) or later. Users should avoid installing plug-ins from untrusted sources.
- Consultation2.0 h
- Implementation1.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9066 — 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-9066 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