CVE-2019-5254
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 an out-of-bounds read vulnerability. An attacker who logs in to the board may send crafted messages from the internal network port or tamper with inter-process message packets to exploit this vulnerability. Due to insufficient validation of the message, successful exploit may cause the affected board to be abnormal.
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 confidenceOut-of-bounds read vulnerability in multiple Huawei network and security products. An authenticated attacker with board access can send specially crafted messages from the internal network port or tamper with inter-process message packets to trigger the vulnerability. Insufficient message validation allows the read beyond buffer boundaries, causing the affected board to become abnormal (likely crash/DoS).
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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 product modelLog into the device management interface or run 'display device' or 'display version' command to determine the exact model (Ap2000, Ips, Ngfw, Nip6300, Nip6600, Nip6800, S5700, or Svn5600)Affected if The model matches any of the affected product lines listed in the CVE
-
Determine the firmware versionRun 'display version' or access the firmware information page to retrieve the installed firmware version stringAffected if The installed version matches any of the specific version numbers listed for that product in the CVE (e.g., v200r005c30, v500r001c00spc300, etc.)
-
Verify inter-process communication is enabledCheck the device configuration for inter-process message handling modules, typically via 'display current-configuration | include ipc' or 'display ipc' commands, or inspect configuration files related to board communicationAffected if IPC or board inter-process communication features are enabled and accessible
-
Check internal network port accessibilityReview network configuration and access controls for internal network ports (often labeled as internal management ports or backplane ports) using 'display ip interface' or 'display ip routing-table' commandsAffected if The internal network port is reachable from an authenticated attacker's network position
-
Confirm authentication stateVerify that attacker could obtain valid credentials for the board management interface, check user account configuration via 'display user-interface' or 'display users'Affected if An authenticated attacker with board access exists or could exist
A user is affected if they are running one of the listed product models at any of the specified firmware versions with inter-process communication or internal network port access available to an authenticated attacker.
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 Huawei security patches for this vulnerability to all affected products. Restrict administrative access to trusted personnel and monitor for signs of abnormal board behavior.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5254 — 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-5254 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