CVE-2019-5295
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 Honor V10 smartphones versions earlier than Berkeley-AL20 9.0.0.125(C00E125R2P14T8) have an authorization bypass vulnerability. Due to improper authorization implementation logic, attackers can bypass certain authorization scopes of smart phones by performing specific operations. This vulnerability can be exploited to perform operations beyond the scope of authorization.
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 confidenceAuthorization bypass vulnerability in Huawei Honor V10 smartphones due to improper authorization implementation logic. Attackers can bypass certain authorization scopes and perform operations beyond their permitted access level. The flaw exists in versions earlier than Berkeley-AL20 9.0.0.125(C00E125R2P14T8).
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< berkeley-al20_9.0.0.125\(c00e125r2p14t8\)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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/AC:H/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.
-
Confirm device model is Honor V10 or Honor View 10Navigate to Settings > About Phone > Model Name on the device and verify the model is either 'Honor V10' or 'Honor View 10'Affected if The device is a Huawei Honor V10 or Honor View 10 smartphone
-
Retrieve the firmware build numberGo to Settings > About Phone > Build Number to display the current firmware version string installed on the deviceAffected if The displayed build number differs from or precedes berkeley-al20_9.0.0.125(C00E125R2P14T8)
-
Compare version against affected thresholdCompare the installed build number to 'berkeley-al20_9.0.0.125(C00E125R2P14T8)' using lexicographic string comparison, noting that earlier versions contain lower version numbers in each segmentAffected if The installed version is any build earlier than berkeley-al20_9.0.0.125(C00E125R2P14t8)
-
Check software update statusNavigate to Settings > System > Software Update to query whether a newer firmware version is available from HuaweiAffected if An update to version Berkeley-AL20 9.0.0.125(C00E125R2P14T8) or later is available for installation
The device is affected if it is a Huawei Honor V10/View 10 running firmware build numbers earlier than berkeley-al20_9.0.0.125(C00E125R2P14T8).
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 dataUpdate Huawei Honor V10 devices to version Berkeley-AL20 9.0.0.125(C00E125R2P14T8) or later to remediate the authorization bypass vulnerability.
- Consultation3.0 h
- Implementation2.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5295 — 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-2019-5295 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