cve.bz

CVE-2020-1814 huawei: Race Condition

5.3 mediumEPSS 0.4%

Medium (5.3) in huawei. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
Huawei NIP6800 versions V500R001C30, V500R001C60SPC500, and V500R005C00; Secospace USG6600 and USG9500 versions V500R001C30SPC200, V500R001C30SPC600, V500R001C60SPC500, and V500R005C00 have a Dangling pointer dereference vulnerability. An authenticated attacker may do some special operations in the affected products in some special scenarios to exploit the vulnerability. Due to improper race conditions of different operations, successful exploit will lead to Dangling pointer dereference, causing some service abnormal.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-1814 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-1814?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-1814?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-1814 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
huawei:nip6800_firmwarev500r001c30
huawei:nip6800_firmwarev500r001c60spc500
huawei:nip6800_firmwarev500r005c00
huawei:secospace_usg6600_firmwarev500r001c30spc200
huawei:secospace_usg6600_firmwarev500r001c30spc600
huawei:secospace_usg6600_firmwarev500r001c60spc500
huawei:secospace_usg6600_firmwarev500r005c00
huawei:usg9500_firmwarev500r001c30spc200
huawei:usg9500_firmwarev500r001c30spc600
huawei:usg9500_firmwarev500r001c60spc500
huawei:usg9500_firmwarev500r005c00

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).

References

Check your stackJSON