dbcve.org
Ar120 S FirmwareOperating system · Huawei

CVE-2019-5293

MEDIUM · 6.5 CVSS v3.1 Published 2019-11-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 memory leak vulnerability when handling some messages. A remote attacker with operation privilege could exploit the vulnerability by sending specific messages continuously. Successful exploit may cause some service 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 confidence

Memory leak vulnerability in Huawei products occurs when the system fails to properly deallocate memory while processing specific messages. An authenticated remote attacker with operation privileges can send specially crafted messages repeatedly to trigger the leak, eventually causing the affected service to become unstable or unavailable.

MitigationRestrict and validate message processing permissions, implement proper memory management and cleanup routines, monitor for abnormal memory consumption patterns, and apply vendor-provided patches when available.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/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 checks

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

  1. Identify the Huawei AR model
    Log into the device CLI and run 'display device' or 'display version' to confirm the exact model number (Ar120-S, Ar1200, Ar150, etc.)
    Affected if The model is any of the affected series: Ar120-S, Ar1200, Ar1200-S, Ar150, Ar150-S, Ar160, Ar200, or Ar200-S
  2. Check installed firmware version
    Run 'display version' in the device CLI to retrieve the current firmware version string
    Affected if The firmware version is exactly v200r005c20 or exactly v200r006c10
  3. Verify remote operation access is enabled
    Check if remote management protocols (Telnet, SSH, SNMP, or web UI) are enabled by reviewing 'user-interface' configuration and checking if operation privileges can be granted to remote users
    Affected if Remote operation access is permitted (the vulnerability requires an authenticated attacker with operation privileges to send crafted messages)
  4. Monitor for abnormal memory consumption
    Periodically run 'display memory-usage' or 'display memory-usage summary' in the CLI to observe memory trends over time
    Affected if Memory usage shows continuous growth or fails to return to baseline after message processing operations, indicating a potential memory leak

You are affected if your device is one of the listed AR models AND runs firmware version v200r005c20 or v200r006c10, with remote operation access enabled.

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

Restrict and validate message processing permissions, implement proper memory management and cleanup routines, monitor for abnormal memory consumption patterns, and apply vendor-provided patches when available.

Fix this in Ar120 S Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5293 — 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-5293 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