CVE-2020-9064
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 smartphone Honor V30 with versions earlier than OxfordS-AN00A 10.0.1.167(C00E166R4P1) have an improper authentication vulnerability. Authentication to target component is improper when device performs an operation. Attackers exploit this vulnerability to obtain some information by loading malicious application, leading to information leak.
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 V30 smartphone has an improper authentication vulnerability in a target component where authentication fails to properly validate credentials during certain device operations. Attackers exploit this by installing a malicious application that bypasses the faulty authentication mechanism to obtain sensitive information, leading to an information leak.
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<= oxfords-an00a_10.0.1.167\(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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Verify Honor V30 device modelNavigate to Settings > About Phone > Model Number and confirm the device is Honor V30 or its model number (oxfords-an00a or similar)Affected if Device model is Honor V30 and the firmware version is at or below oxfords-an00a_10.0.1.167(C00E166R4P1)
-
Check installed firmware versionNavigate to Settings > About Phone > Version > Build Number and compare the full version string to the affected rangeAffected if Build number is oxfords-an00a_10.0.1.167(C00E166R4P1) or earlier (numerically or alphabetically lower)
-
Confirm target component is presentCheck if the device contains the specific authentication component that handles credential validation for device operations (this may be observable through system app listings or permissions on the device)Affected if The vulnerable authentication component exists and handles credential validation for the affected operations
-
Verify app installation capabilityConfirm the device allows installation of applications from sources outside the official app store (check Settings > Security > Unknown Sources or Settings > Apps > Special Access > Install Unknown Apps)Affected if Unknown app sources are enabled, allowing a malicious application to be installed to exploit the authentication bypass
A user is affected if they have a Honor V30 device running firmware version oxfords-an00a_10.0.1.167(C00E166R4P1) or earlier and the vulnerable authentication component is active on the device.
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 dataUpgrade the Honor V30 firmware to version OxfordS-AN00A 10.0.1.167(C00E166R4P1) or later to remediate the improper authentication vulnerability.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9064 — 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-9064 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