CVE-2019-5256
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 · uneditedCertain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981) have a null pointer dereference vulnerability. The system dereferences a pointer that it expects to be valid, but is NULL. A local attacker could exploit this vulnerability by sending crafted parameters. A successful exploit could cause a denial of service and the process 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 · high confidenceMultiple Huawei products contain a null pointer dereference vulnerability where the system dereferences a pointer that it expects to be valid but is NULL. A local attacker with the ability to send crafted parameters can trigger this condition, causing denial of service and process 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= v200r005c30= v200r006c10= v200r006c20= v200r007c10= v200r007c20= v200r008c00= v200r008c10= v200r009c00= v500r001c00spc300= v500r001c00spc500= v500r001c00sph303= v500r001c00sph508= v500r001c20= v500r001c20spc100= v500r001c20spc100pwe= v500r001c20spc200= v500r001c20spc200b062= v500r001c20spc200pwe= v500r001c20spc300b078= v500r001c20spc300pwe= v500r001c00spc300= v500r001c00spc500= v500r001c00spc500pwe= v500r001c00sph303= v500r001c00sph508= v500r001c20= v500r001c20spc100= v500r001c20spc100pwe= v500r001c20spc200= v500r001c20spc200b062= v500r001c20spc200pwe= v500r001c20spc300b078= v500r001c00spc300= v500r001c00spc500= v500r001c00sph303= v500r001c00sph508= v500r001c20= v500r001c20spc100= v500r001c20spc100pwe= v500r001c20spc200= v500r001c20spc200b062= v500r001c20spc200pwe= v500r001c20spc300b078= v500r001c20spc300pwe= v500r001c00spc300= v500r001c00spc500= v500r001c00sph303= v500r001c00sph508= v500r001c20= v500r001c20spc100= v500r001c20spc100pwe= v500r001c20spc200= v500r001c20spc200b062= v500r001c20spc200pwe= v500r001c20spc300b078= v500r001c30= v500r001c50= v500r001c50pwe= v500r001c80= v500r005c00= v200r005c03= v200r003c00spc100CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/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 Huawei product modelLog into the device management interface or check the device label to determine the exact model (Ap2000, Ips, Ngfw, Nip6300, Nip6600, Nip6800, S5700, or Svn5600)Affected if The device is any of these eight models
-
Retrieve the firmware versionAccess the device CLI or web management interface and run the command to display the firmware version (commonly 'display version' or check the system info page)Affected if The installed version matches one of the specific versions listed for that product
-
Compare version against affected listMatch your retrieved firmware version exactly against the list of affected versions provided in the CVE (e.g., for Ap2000: v200r005c30, v200r006c10, v200r006c20, v200r007c10, v200r007c20, v200r008c00, v200r008c10, v200r009c00)Affected if Your version appears verbatim in the affected versions list
-
Verify local attack vector accessibilityDetermine if an attacker could access the local management interface or CLI where they can send crafted parameters. Check authentication controls and user access logs for unauthorized local access attemptsAffected if Unauthenticated or low-privilege local users can send parameters to the affected component
-
Check for denial of service indicatorsReview system logs and process status for unexpected process crashes, reboots, or service interruptions that correlate with parameter inputsAffected if Processes are crashing or rebooting unexpectedly and correlate with parameter manipulation attempts
You are affected if your Huawei device model matches one of the eight products AND your installed firmware version exactly matches a version listed in the affected versions list for that product.
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 patch from Huawei for affected products. Until patched, limit local access and monitor for suspicious parameter inputs to reduce exploitability.
- Consultation4.0 h
- Implementation2.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 $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5256 — 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-5256 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