dbcve.org
Ar120 S FirmwareOperating system · Huawei

CVE-2019-5304

HIGH · 7.5 CVSS v3.1 Published 2020-01-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Some Huawei products have a buffer error vulnerability. An unauthenticated, remote attacker could send specific MPLS Echo Request messages to the target products. Due to insufficient input validation of some parameters in the messages, successful exploit may cause the device to reset.

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 confidence

A buffer error vulnerability exists in Huawei products where specific MPLS Echo Request messages are not properly validated. An unauthenticated remote attacker can send crafted MPLS packets with insufficient input validation of certain parameters, triggering a buffer overflow that causes the device to reset.

MitigationApply available Huawei firmware patches for this vulnerability. If no patch is available, consider filtering MPLS traffic at network boundaries or disabling MPLS features if not required, and restrict network access to trusted sources.

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
Ar120 S FirmwareOperating system
Affected:= v200r006c10= v200r007c00= v200r008c20= v200r008c50
Ar1200 FirmwareOperating system
Affected:= v200r003c01= v200r005c20= v200r006c10= v200r007c00= v200r008c20= v200r008c50
Ar1200 S FirmwareOperating system
Affected:= v200r003c01= v200r005c20= v200r006c10= v200r007c00= v200r008c20= v200r008c50
Ar150 FirmwareOperating system
Affected:= v200r003c01= v200r005c20= v200r006c10= v200r007c00= v200r008c20= v200r008c50
Ar150 S FirmwareOperating system
Affected:= v200r003c01= v200r005c20= v200r006c10= v200r007c00= v200r008c20= v200r008c50
Ar160 FirmwareOperating system
Affected:= v200r005c20= v200r006c10= v200r007c00= v200r008c20= v200r008c50
Ar200 FirmwareOperating system
Affected:= v200r003c01= v200r005c20= v200r006c10= v200r007c00= v200r008c20= v200r008c50
Ar200 S FirmwareOperating system
Affected:= v200r003c01= v200r005c20= v200r006c10= v200r007c00= v200r008c20= v200r008c50

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Huawei AR device model
    Run 'display device' or 'display version' command on the Huawei device to confirm the exact model (Ar120 S, Ar1200, Ar1200 S, Ar150, Ar150 S, Ar160, Ar200, or Ar200 S)
    Affected if Device is any of these eight AR models
  2. Check the installed firmware version
    Run 'display version' command to retrieve the installed firmware version string
    Affected if Version matches any of: v200r003c01, v200r005c20, v200r006c10, v200r007c00, v200r008c20, or v200r008c50
  3. Verify if MPLS feature is enabled
    Run 'display mpls interface' or 'display mpls lsp' to check whether MPLS is configured and active on the device
    Affected if MPLS is enabled and running on any interface
  4. Assess MPLS network exposure
    Review network configuration and ACLs to determine whether MPLS traffic from untrusted or external sources can reach this device
    Affected if Device can receive MPLS Echo Request packets from unauthenticated or untrusted network sources

Device is affected if it is one of the listed Huawei AR models, runs one of the specified firmware versions, has MPLS enabled, and can receive MPLS packets from untrusted network sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply available Huawei firmware patches for this vulnerability. If no patch is available, consider filtering MPLS traffic at network boundaries or disabling MPLS features if not required, and restrict network access to trusted sources.

Fix this in Ar120 S Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-5304 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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