CVE-2020-9094
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 an out of bound read vulnerability in some verisons of Huawei CloudEngine product. A module does not deal with specific message properly. Attackers can exploit this vulnerability by sending malicious packet. This can lead to denial of service.
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 confidenceAn out-of-bounds read vulnerability exists in certain Huawei CloudEngine product modules that fail to properly handle specific message types. Attackers can exploit this by sending specially crafted malicious packets to trigger the out-of-bounds read, resulting in denial of service.
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= v200r019c00spc800= v200r019c00spc800= v200r005c20spc800= v200r019c00spc800= v200r019c00spc800CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 CloudEngine modelLog into the device CLI and run 'display device' or 'display version' to confirm the hardware model (12800, 5800, 6800, or 7800)Affected if The model is CloudEngine 12800, 5800, 6800, or 7800
-
Check firmware versionRun 'display version' in the device CLI to obtain the current firmware version stringAffected if The installed version matches v200r019c00spc800 or v200r005c20spc800 for the identified model
-
Identify active modules handling network messagesRun 'display interface' or 'display ip interface' to see which logical interfaces and protocols are active; the vulnerability affects modules that process specific message typesAffected if Network message handling modules are active and processing external packet traffic
-
Review logs for exploitation indicatorsRun 'display logbuffer' or 'display trapbuffer' to check for unexpected errors, crashes, or denial of service indicators that may correlate with the vulnerabilityAffected if Logs show repeated crashes, memory errors, or service interruptions tied to packet processing
You are affected if you run a CloudEngine 12800, 5800, 6800, or 7800 with firmware version v200r019c00spc800 or v200r005c20spc800 and the vulnerable message handling module is active processing traffic.
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 vendor-provided patches for affected CloudEngine versions when available. As an interim measure, implement network segmentation and filter or block malicious packet patterns at perimeter defenses to reduce attack surface.
- 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-9094 — 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-9094 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