CVE-2020-1792
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 · uneditedHonor V10 smartphones with versions earlier than BKL-AL20 10.0.0.156(C00E156R2P4) and versions earlier than BKL-L09 10.0.0.146(C432E4R1P4) have an out of bounds write vulnerability. The software writes data past the end of the intended buffer because of insufficient validation of certain parameter when initializing certain driver program. An attacker could trick the user into installing a malicious application, successful exploit could cause the device to reboot.
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 confidenceHonor V10 smartphones have an out-of-bounds write vulnerability in driver initialization code. Insufficient validation of a parameter during driver initialization allows a malicious application to write beyond the intended buffer boundary, causing device reboot.
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< bkl-al20_10.0.0.156\(c00e156r2p4\)< bkl-l09_10.0.0.146\(c432e4r1p4\)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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 model numberCheck the device settings or use AT commands to confirm the model is Honor V10 with model numbers BKL-AL20 or BKL-L09Affected if Model is BKL-AL20 or BKL-L09 and firmware version is below the patched versions
-
Check BKL-AL20 firmware versionNavigate to Settings > About Phone > Version on the Honor V10 or use engineering mode to view the exact build number (bkl-al20_10.0.0.156(c00e156r2p4))Affected if Firmware build number is less than bkl-al20_10.0.0.156(c00e156r2p4)
-
Check BKL-L09 firmware versionNavigate to Settings > About Phone > Version on the Honor V10 or use engineering mode to view the exact build number (bkl-l09_10.0.0.146(c432e4r1p4))Affected if Firmware build number is less than bkl-l09_10.0.0.146(c432e4r1p4)
-
Verify vulnerable driver presenceThe vulnerability exists in the driver initialization code - confirm the driver module is present on the device (specific driver name not provided in CVE details)Affected if Driver is present and device model/version is within affected range
Device is affected if it is an Honor V10 (BKL-AL20 or BKL-L09) running firmware versions below bkl-al20_10.0.0.156(c00e156r2p4) or bkl-l09_10.0.0.146(c432e4r1p4) respectively.
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 Honor V10 to the patched versions: BKL-AL20 to 10.0.0.156(C00E156R2P4) or later, and BKL-L09 to 10.0.0.146(C432E4R1P4) or later. Avoid installing applications from untrusted sources.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1792 — 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-1792 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