CVE-2020-9071
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 · uneditedThere is a few bytes out-of-bounds read vulnerability in some Huawei products. The software reads data past the end of the intended buffer when parsing certain message, an authenticated attacker could exploit this vulnerability by sending crafted messages to the device. Successful exploit may cause service abnormal in specific scenario.Affected product versions include:AR120-S versions V200R007C00SPC900,V200R007C00SPCa00
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 confidenceThis is an out-of-bounds read vulnerability in Huawei AR120-S routers where the software reads data past the end of the intended buffer when parsing certain crafted messages. An authenticated attacker can exploit this vulnerability by sending specially crafted messages to the device, potentially causing service abnormalities.
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= v200r007c00spc900= v200r007c00spca00= v200r007c00spcb00= v200r007c00spcc00= v200r007c00spc900= v200r007c00spc900pwe= v200r007c00spca00= v200r007c00spcb00= v200r007c00spcb00pwe= v200r007c00spcc00= v200r007c00spc900= v200r007c00spcb00= v200r007c00spcc00= v200r007c00spc900= v200r007c00spc900pwe= v200r007c00spcb00= v200r007c00spcb00pwe= v200r007c00spcc00= v200r007c00spc900= v200r007c00spcb00= v200r007c00spcc00= v200r007c00spc900= v200r007c00spc900pwe= v200r007c00spcb00= v200r007c00spcb00pwe= v200r007c00spcc00= v200r007c00spc900= v200r007c00spc900pwe= v200r007c00spcb00= v200r007c00spcb00pwe= v200r007c00spcc00= v200r007c00spc900= v200r007c00spcb00= v200r007c00spcc00CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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 the router modelLog into the device or check the device label/management interface to confirm the exact model (AR120-S, AR1200, AR1200 S, AR150, AR150 S, AR160, AR200, or AR200 S)Affected if The device model is NOT one of these eight affected models - you are not affected
-
Check the firmware versionRun the command 'display version' in the device CLI or check the firmware version through the management interfaceAffected if The firmware version matches any of: v200r007c00spc900, v200r007c00spca00, v200r007c00spcb00, v200r007c00spcc00, or their pwe variants - proceed to next check
-
Verify authentication requirementConfirm whether the device management interface (CLI, web, or SNMP) is accessible to untrusted usersAffected if Untrusted or anonymous users can authenticate to the device - you may be at risk; if only trusted administrators have access, the attack surface is reduced
You are affected if your device is an AR120-S, AR1200, AR1200 S, AR150, AR150 S, AR160, AR200, or AR200 S running firmware version v200r007c00spc900, v200r007c00spca00, v200r007c00spcb00, or v200r007c00spcc00 (or pwe variants) AND the management interface is accessible to untrusted authenticated users.
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 dataApply the vendor-supplied firmware update from Huawei to the affected AR120-S versions. If no update is available, restrict administrative access to trusted authenticated users only to reduce the attack surface.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9071 — 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-9071 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