cve.bz

CVE-2019-5300 huawei

6.7 mediumEPSS 0.2%

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

On this page
There is a digital signature verification bypass vulnerability in AR1200, AR1200-S, AR150, AR160, AR200, AR2200, AR2200-S, AR3200, SRG1300, SRG2300 and SRG3300 Huawei routers. The vulnerability is due to the affected software improperly verifying digital signatures for the software image in the affected device. A local attacker with high privilege may exploit the vulnerability to bypass integrity checks for software images and install a malicious software image on the affected device.

Severity

CVSS 3.0

6.7 medium
CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-347 Improper Verification of Cryptographic Signature
OWASP Top 10
A04:2025 Cryptographic Failures
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-2019-5300 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-5300?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-5300?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-2019-5300 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:ar1200_firmwarev200r007c00
huawei:ar1200_firmwarev200r008c20
huawei:ar1200_firmwarev200r008c50
huawei:ar1200_firmwarev200r009c00
huawei:ar1200_firmwarev200r010c00
huawei:ar1200-s_firmwarev200r007c00
huawei:ar1200-s_firmwarev200r008c20
huawei:ar1200-s_firmwarev200r008c50
huawei:ar1200-s_firmwarev200r009c00
huawei:ar1200-s_firmwarev200r010c00
huawei:ar150_firmwarev200r007c00
huawei:ar150_firmwarev200r008c20
huawei:ar150_firmwarev200r008c50
huawei:ar150_firmwarev200r009c00
huawei:ar150_firmwarev200r010c00
huawei:ar160_firmwarev200r007c00
huawei:ar160_firmwarev200r008c20
huawei:ar160_firmwarev200r008c50
huawei:ar160_firmwarev200r009c00
huawei:ar160_firmwarev200r010c00
huawei:ar200_firmwarev200r007c00
huawei:ar200_firmwarev200r008c20
huawei:ar200_firmwarev200r008c50
huawei:ar200_firmwarev200r009c00
huawei:ar200_firmwarev200r010c00
huawei:ar2200_firmwarev200r007c00
huawei:ar2200_firmwarev200r008c20
huawei:ar2200_firmwarev200r008c50
huawei:ar2200_firmwarev200r009c00
huawei:ar2200_firmwarev200r010c00
huawei:ar2200s_firmwarev200r007c00
huawei:ar2200s_firmwarev200r008c20
huawei:ar2200s_firmwarev200r008c50
huawei:ar2200s_firmwarev200r009c00
huawei:ar2200s_firmwarev200r010c00
huawei:ar3200_firmwarev200r007c00
huawei:ar3200_firmwarev200r008c20
huawei:ar3200_firmwarev200r008c50
huawei:ar3200_firmwarev200r009c00
huawei:ar3200_firmwarev200r010c00
huawei:srg1300_firmwarev200r007c00
huawei:srg1300_firmwarev200r008c50
huawei:srg1300_firmwarev200r009c00
huawei:srg1300_firmwarev200r010c00
huawei:srg2300_firmwarev200r007c00
huawei:srg2300_firmwarev200r008c50
huawei:srg2300_firmwarev200r009c00
huawei:srg2300_firmwarev200r010c00
huawei:srg3300_firmwarev200r007c00
huawei:srg3300_firmwarev200r008c50
huawei:srg3300_firmwarev200r009c00
huawei:srg3300_firmwarev200r010c00

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON