How severe is CVE-2019-5256?

CVE-2019-5256 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2019-5256 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (11th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-5256?

CVE-2019-5256 primarily affects Huawei Ap2000 Firmware. In total, 244 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2019-5256?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2019-5256 published?

CVE-2019-5256 was published on 2019-12-13 and last updated on 2026-06-17.

CVE-2019-5256

CVE-2019-5256 is a medium-severity vulnerability in Huawei Ap2000 Firmware with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-476.

Key facts

Severity: Medium (CVSS 3.x base score 5.5)
CVSS v2: 2.1
EPSS exploit prediction: 0% (11th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-476
Affected product: Huawei Ap2000 Firmware
Published: 2019-12-13
Last modified: 2026-06-17

Description

Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981) have a null pointer dereference vulnerability. The system dereferences a pointer that it expects to be valid, but is NULL. A local attacker could exploit this vulnerability by sending crafted parameters. A successful exploit could cause a denial of service and the process reboot.

Frequently asked questions

What is CVE-2019-5256?: Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;Secospace AntiDDoS8000;Secospace USG6300;Secospace USG6500;Secospace USG6600;USG6000V;eSpace U1981) have a null pointer dereference vulnerability. The system dereferences a pointer that it expects to be valid, but is NULL. A local attacker could exploit this vulnerability by sending crafted parameters. A successful exploit could cause a denial of service and the process reboot.
How severe is CVE-2019-5256?: CVE-2019-5256 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2019-5256 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (11th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-5256?: CVE-2019-5256 primarily affects Huawei Ap2000 Firmware. In total, 244 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2019-5256?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2019-5256 published?: CVE-2019-5256 was published on 2019-12-13 and last updated on 2026-06-17.

References

https://www.huawei.com/en/psirt/security-advisories/huawei-sa-20191211-01-ssp-en

Affected products (244)

cpe:2.3:o:huawei:ap2000_firmware:v200r005c30:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ap2000_firmware:v200r006c10:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ap2000_firmware:v200r006c20:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ap2000_firmware:v200r007c10:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ap2000_firmware:v200r007c20:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ap2000_firmware:v200r008c00:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ap2000_firmware:v200r008c10:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ap2000_firmware:v200r009c00:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c00spc300:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c00spc500:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c00sph303:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c00sph508:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c20:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c20spc100:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c20spc100pwe:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c20spc200:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c20spc200b062:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c20spc200pwe:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c20spc300b078:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c20spc300pwe:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c30:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c30spc100:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c30spc100pwe:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c30spc200:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c30spc200pwe:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c30spc300:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c50:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c50pwe:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r001c80:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ips_firmware:v500r005c00:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ngfw_firmware:v500r001c00spc300:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ngfw_firmware:v500r001c00spc500:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ngfw_firmware:v500r001c00spc500pwe:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ngfw_firmware:v500r001c00sph303:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ngfw_firmware:v500r001c00sph508:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ngfw_firmware:v500r001c20:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ngfw_firmware:v500r001c20spc100:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ngfw_firmware:v500r001c20spc100pwe:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ngfw_firmware:v500r001c20spc200:*:*:*:*:*:*:*
cpe:2.3:o:huawei:ngfw_firmware:v500r001c20spc200b062:*:*:*:*:*:*:*

More vulnerabilities in Huawei Ap2000 Firmware

CVE-2019-5254 — High (CVSS 8.6): Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;…
CVE-2019-5258 — Medium (CVSS 5.5): Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;…
CVE-2019-5257 — Medium (CVSS 5.5): Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;…
CVE-2019-5255 — Medium (CVSS 5.5): Certain Huawei products (AP2000;IPS Module;NGFW Module;NIP6300;NIP6600;NIP6800;S5700;SVN5600;SVN5800;SVN5800-C;SeMG9811;…

All CVEs affecting Huawei Ap2000 Firmware →

Other CWE-476 (NULL Pointer Dereference) vulnerabilities

CVE-2022-36648 — Critical (CVSS 10.0): The hardware emulation in the of_dpa_cmd_add_l2_flood of rocker device model in QEMU, as used in 7.0.0 and earlier,…
CVE-2020-14500 — Critical (CVSS 10.0): Secomea GateManager all versions prior to 9.2c, An attacker can send a negative value and overwrite arbitrary data.
CVE-2010-2495 — Critical (CVSS 10.0): The pppol2tp_xmit function in drivers/net/pppol2tp.c in the L2TP implementation in the Linux kernel before 2.6.34 does…
CVE-2026-46195 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: smb: client: validate dacloffset before building…
CVE-2026-31657 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: batman-adv: hold claim backbone gateways by…
CVE-2026-31436 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: fix possible wrong descriptor…

Browse all CWE-476 (NULL Pointer Dereference) vulnerabilities →