CVE-2019-5291: Some Huawei products have an insufficient verification of data authenticity vulnerability.
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Some Huawei products have an insufficient verification of data authenticity vulnerability. A remote, unauthenticated attacker has to intercept specific packets between two devices, modify the packets, and send the modified packets to the peer device. Due to insufficient verification of some fields in the packets, an attacker may exploit the vulnerability to cause the target device to be abnormal.
- Published
- Dec 13, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- CWE-345
Report tools
Action score
23
Monitor
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| huawei | ar120-s firmware | cpe:2.3:o:huawei:ar120-s_firmware |
| huawei | ar120-s | cpe:2.3:h:huawei:ar120-s |
| huawei | ar1200 firmware | cpe:2.3:o:huawei:ar1200_firmware |
| huawei | ar1200 | cpe:2.3:h:huawei:ar1200 |
| huawei | ar1200-s firmware | cpe:2.3:o:huawei:ar1200-s_firmware |
| huawei | ar1200-s | cpe:2.3:h:huawei:ar1200-s |
| huawei | ar150 firmware | cpe:2.3:o:huawei:ar150_firmware |
| huawei | ar150 | cpe:2.3:h:huawei:ar150 |
| huawei | ar150-s firmware | cpe:2.3:o:huawei:ar150-s_firmware |
| huawei | ar150-s | cpe:2.3:h:huawei:ar150-s |
| huawei | ar160 firmware | cpe:2.3:o:huawei:ar160_firmware |
| huawei | ar160 | cpe:2.3:h:huawei:ar160 |
and 24 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- huawei ar120-s firmwarev200r005c20
- huawei ar120-s firmwarev200r006c10
- huawei ar120-s firmwarev200r007c00
- huawei ar120-s firmwarev200r008c50
- huawei ar1200 firmwarev200r005c00
- huawei ar1200 firmwarev200r006c10
- huawei ar1200 firmwarev200r007c00
- huawei ar1200 firmwarev200r008c50
- huawei ar1200-s firmwarev200r005c20
- huawei ar1200-s firmwarev200r006c10
- huawei ar1200-s firmwarev200r007c00
- huawei ar1200-s firmwarev200r008c50
- huawei ar150 firmwarev200r005c20
- huawei ar150 firmwarev200r006c10
- huawei ar150 firmwarev200r007c00
- huawei ar150 firmwarev200r008c50
- huawei ar150-s firmwarev200r005c20
- huawei ar150-s firmwarev200r006c10
- huawei ar150-s firmwarev200r007c00
- huawei ar150-s firmwarev200r008c50
Versions reported by the vendor
Affected version ranges reported by the assigning authority (huawei). Independent of NVD's CPE analysis and usually ahead of it.
n/a AR120-S;AR1200;AR1200-S;AR150;AR150-S;AR160;AR200;AR200-S;AR2200;AR2200-S;AR3200;AR3600;CloudEngine 12800;NetEngine16EX;S6700;SRG1300;SRG2300;SRG3300
- V200R005C20, V200R006C10, V200R007C00, V200R008C50, V200R005C00, V200R002C10, V200R002C20, V200R008C00, V200R010C00SPC300, V200R010C00SPC600, V200R011C00SPC200affected
Same product
huawei: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-17301Huawei AR120-S V200R005C32, V200R006C10, V200R007C00, V200R008C20, AR1200 V200R005C20, V200R005C32, V200R006C10, V200R007C00, V200R007C01, V39Monitor
- CVE-2019-19417The SIP module of some Huawei products have a denial of service (DoS) vulnerability.30Monitor
- CVE-2019-19416The SIP module of some Huawei products have a denial of service (DoS) vulnerability.30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2019-5293Nov 13, 2019 · Some Huawei products have a memory leak vulnerability when handling some messages.26Monitor
- ← EarlierCVE-2019-5294Nov 13, 2019 · There is an out of bound read vulnerability in some Huawei products.30Monitor
- Later →CVE-2019-5259Dec 16, 2019 · There is an information leakage vulnerability on some Huawei products(AR120-S;AR1200;AR1200-S;AR150;AR150-S;AR160;AR200;AR200-S;AR2200;AR22026Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-105 · Feb 20, 2020(Huawei Ürünleri için Güvenlik Güncellemesi Yayınladı)
- TR-20-075 · Feb 5, 2020(Huawei Ürünleri için Güvenlik Güncellemesi Yayınladı)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-345 · Insufficient Verification of Data AuthenticityCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- JSON Hijacking (aka JavaScript Hijacking)CAPEC-111likelihood: High · High
- Cache PoisoningCAPEC-141likelihood: High · High
- DNS Cache PoisoningCAPEC-142likelihood: High · High
- Content SpoofingCAPEC-148likelihood: Medium · Medium
- Spoofing of UDDI/ebXML MessagesCAPEC-218Medium
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
- Application API Navigation RemappingCAPEC-386Medium
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.