dbcve.org
Ips Module FirmwareOperating system · Huawei

CVE-2020-1823

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
There are multiple out of bounds (OOB) read vulnerabilities in the implementation of the Common Open Policy Service (COPS) protocol of some Huawei products. The specific decoding function may occur out-of-bounds read when processes an incoming data packet. Successful exploit of these vulnerabilities may disrupt service on the affected device. (Vulnerability ID: HWPSIRT-2018-12275,HWPSIRT-2018-12276,HWPSIRT-2018-12277,HWPSIRT-2018-12278,HWPSIRT-2018-12279,HWPSIRT-2018-12280 and HWPSIRT-2018-12289) The seven vulnerabilities have been assigned seven Common Vulnerabilities and Exposures (CVE) IDs: CVE-2020-1818, CVE-2020-1819, CVE-2020-1820, CVE-2020-1821, CVE-2020-1822, CVE-2020-1823 and CVE-2020-1824.

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

Out-of-bounds (OOB) read vulnerabilities exist in the COPS (Common Open Policy Service) protocol implementation of certain Huawei products. The vulnerabilities reside in the decoding function that processes incoming data packets, where improper bounds checking allows reading memory outside allocated buffers. Successful exploitation can disrupt service on affected devices.

MitigationApply Huawei-supplied patches for the affected products (refer to Huawei advisory HWPSIRT-2018-12275 through HWPSIRT-2018-12289). If patches are unavailable, consider disabling the COPS protocol or implementing network-level filtering to limit exposure to untrusted COPS traffic.

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
Ips Module FirmwareOperating system
Affected:= v500r001c30= v500r001c60= v500r005c00
Ngfw Module FirmwareOperating system
Affected:= v500r002c00= v500r002c20= v500r005c00
Nip6300 FirmwareOperating system
Affected:= v500r001c30= v500r001c60= v500r005c00
Nip6600 FirmwareOperating system
Affected:= v500r001c30= v500r001c60= v500r005c00
Nip6800 FirmwareOperating system
Affected:= v500r001c60= v500r005c00
Secospace Usg6300 FirmwareOperating system
Affected:= v500r001c30= v500r001c60= v500r005c00
Secospace Usg6500 FirmwareOperating system
Affected:= v500r001c30= v500r001c60= v500r005c00
Secospace Usg6600 FirmwareOperating system
Affected:= v500r001c30= v500r005c00

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 device model and firmware version
    Access the device management interface or use the command line (e.g., display version, system-view, display device version) to retrieve the exact product model and firmware version
    Affected if The firmware version matches one of the affected versions: v500r001c30, v500r001c60, v500r002c00, v500r002c20, or v500r005c00 for the listed product lines (Ips Module, Ngfw Module, Nip6300, Nip6600, Nip6800, Secospace Usg6300, Usg6500, Usg6600)
  2. Confirm COPS protocol is enabled
    Check the device configuration for COPS protocol settings. Typically done via command line with commands like display cops configuration or by reviewing the policy configuration files
    Affected if COPS protocol is enabled and configured on the device
  3. Verify COPS is actively listening or processing traffic
    Check active listening ports and services, typically via display ip interface or display service-port, looking for port 3288 (standard COPS port) or custom COPS configurations
    Affected if The device is listening on COPS ports or has active COPS sessions established

The device is affected if it runs one of the listed firmware versions AND has COPS protocol enabled and processing incoming packets.

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 Huawei-supplied patches for the affected products (refer to Huawei advisory HWPSIRT-2018-12275 through HWPSIRT-2018-12289). If patches are unavailable, consider disabling the COPS protocol or implementing network-level filtering to limit exposure to untrusted COPS traffic.

Fix this in Ips Module Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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