CVE-2019-5248
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 · uneditedCloudEngine 12800 has a DoS vulnerability. An attacker of a neighboring device sends a large number of specific packets. As a result, a memory leak occurs after the device uses the specific packet. As a result, the attacker can exploit this vulnerability to cause DoS attacks on the target device.
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 confidenceMemory leak vulnerability in Huawei CloudEngine 12800 switches where processing of specially crafted packets from an adjacent attacker causes memory exhaustion, leading to denial of service. The attacker sends a large number of specific packets from a neighboring device that trigger the memory leak when processed by the device.
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= v200r001c00spc600= v200r001c00spc700= v200r002c01= v200r002c50spc800= v200r002c50spc800pweCVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/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 device modelRun 'display device' or check physical device labeling to confirm it is a CloudEngine 12800 switchAffected if Device is not a CloudEngine 12800, then not affected by this specific CVE
-
Check the firmware versionRun 'display version' or 'display device version' to obtain the current firmware versionAffected if Version matches any of these: v200r001c00spc600, v200r001c00spc700, v200r002c01, v200r002c50spc800, v200r002c50spc800pwe
-
Verify adjacent network exposureReview network configuration to determine if untrusted adjacent devices can send packets to this switch (check port access settings, VLAN configurations, and trust boundaries)Affected if The switch accepts packets from untrusted adjacent devices on the network
-
Check for memory exhaustion symptomsRun 'display memory usage' or 'display memory-usage' to check current memory utilizationAffected if Memory usage is abnormally high or continuously increasing without returning to baseline
-
Inspect for unusual traffic patternsRun 'display traffic statistics' or check traffic counters on inbound interfaces for unexpected packet volumes from adjacent devicesAffected if Unusually high packet rates from neighboring devices are observed
A user is affected if they have a CloudEngine 12800 running one of the listed firmware versions and the device is exposed to adjacent network traffic from potentially untrusted devices.
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 or firmware updates from Huawei for the CloudEngine 12800. If patches are unavailable, implement network segmentation to restrict adjacent device access and monitor for unusual traffic patterns.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5248 — 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-5248 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