CVE intelligence and bounded remediation

CVE-2020-9067 — There is a buffer overflow vulnerability in some Huawei products

High CVSS 8

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.

Severity
High
CVSS
8 (3.1)
Published
2020-04-02
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-120

Affected products

  • huawei / smartax_ma5600t_firmware / v800r013c10
  • huawei / smartax_ma5600t_firmware / v800r015c00
  • huawei / smartax_ma5600t_firmware / v800r015c10
  • huawei / smartax_ma5600t_firmware / v800r017c00
  • huawei / smartax_ma5600t_firmware / v800r017c10
  • huawei / smartax_ma5600t_firmware / v800r018c00

Showing 6 representative product identities from 15 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Buffer bounds, memory safety, and memory corruption

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Identify affected native-code versions, build flags, architectures, parsers, codecs, drivers, and input paths in all shipped artifacts.
  • Determine whether untrusted data reaches the affected routine and the process privilege, sandbox, and network exposure.
  • Confirm statically linked, vendored, firmware, and platform-provided copies, not only package-manager records.

Remediate safely

  • Apply the maintained upstream correction or replace the affected component, then rebuild every dependent artifact from clean inputs.
  • Adopt bounds-checked interfaces, validated sizes and integer conversions, clear ownership, and memory-safe components where practical.
  • Enable supported compiler and runtime hardening and add sanitized tests and fuzz regression seeds derived from non-weaponized fixtures.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.