dbcve.org
Smartax Ma5600t FirmwareOperating system · Huawei

CVE-2020-9067

HIGH · 8.0 CVSS v3.1 Published 2020-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
There is a buffer overflow vulnerability in some Huawei products. The vulnerability can be exploited by an attacker to perform remote code execution on the affected products when the affected product functions as an optical line terminal (OLT). Affected product versions include:SmartAX MA5600T versions V800R013C10, V800R015C00, V800R015C10, V800R017C00, V800R017C10, V800R018C00, V800R018C10; SmartAX MA5800 versions V100R017C00, V100R017C10, V100R018C00, V100R018C10, V100R019C10; SmartAX EA5800 versions V100R018C00, V100R018C10, V100R019C10.

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 confidence

A buffer overflow vulnerability exists in Huawei SmartAX OLT products (MA5600T, MA5800, EA5800) that allows remote code execution. The vulnerability is triggered when the affected product operates as an optical line terminal, enabling an attacker to overflow a buffer and execute arbitrary code remotely.

MitigationApply vendor-provided patches or upgrade to fixed versions when available. If no patch exists, implement network segmentation to restrict access to OLT management interfaces and monitor for exploitation attempts.

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
Smartax Ma5600t FirmwareOperating system
Affected:= v800r013c10= v800r015c00= v800r015c10= v800r017c00= v800r017c10= v800r018c00= v800r018c10
Smartax Ma5800 FirmwareOperating system
Affected:= v100r017c00= v100r017c10= v100r018c00= v100r018c10= v100r019c10
Smartax Ea5800 FirmwareOperating system
Affected:= v100r018c00= v100r018c10= v100r019c10

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

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 SmartAX OLT model
    Log into the device CLI or check the hardware label to determine if the model is MA5600T, MA5800, or EA5800. Use commands such as 'display device manufacture' or 'display version' to confirm the model number.
    Affected if The device model is MA5600T, MA5800, or EA5800
  2. Check the installed firmware version
    Execute the Huawei CLI command to display the firmware version, such as 'display version' or 'display bootrom'. Record the exact version string shown.
    Affected if The firmware version matches one of the listed affected versions: MA5600T v800r013c10, v800r015c00, v800r015c10, v800r017c00, v800r017c10, v800r018c00, v800r018c10; MA5800 v100r017c00, v100r017c10, v100r018c00, v100r018c10, v100r019c10; EA5800 v100r018c00, v100r018c10, v100r019c10
  3. Verify OLT functionality is enabled
    Check the device configuration to confirm the optical line terminal (OLT) feature is active. Use commands like 'display service-port' or 'display ont info' to see if PON ports are configured and operational.
    Affected if The device is configured and operating as an OTL with active PON (Passive Optical Network) ports and ONT (Optical Network Terminal) registrations
  4. Confirm remote management access is exposed
    Review the device network configuration for exposed management interfaces such as telnet, SSH, or web UI that are accessible from non-local networks. Use 'display ip interface' or 'display current-configuration | include management' to identify accessible IPs.
    Affected if Management interfaces are reachable from network segments beyond the local OLT management zone

The environment is affected if the device is a Huawei SmartAX MA5600T, MA5800, or EA5800 running one of the listed firmware versions and OLT functionality is enabled with potentially exposed management access.

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 vendor-provided patches or upgrade to fixed versions when available. If no patch exists, implement network segmentation to restrict access to OLT management interfaces and monitor for exploitation attempts.

Fix this in Smartax Ma5600t Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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