Skip to content
Noroxi
CVE-2019-5300· NVD / CVE Program· CNA huawei

There is a digital signature verification bypass vulnerability in AR1200, AR1200-S, AR150, AR160, AR200, AR2200, AR2200-S, AR3200, SRG1300,

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.

MediumCVSS 6.7 · v3.0—No exploit No fix recorded
Published
Jun 4, 2019
Updated
Jun 16, 2026
EPSS
0.2% · 7th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Affected systems

VendorProduct
huaweiar1200 firmware
huaweiar1200e
huaweiar1220c
huaweiar1220ev
huaweiar1220evw
huaweiar1200-s firmware
huaweiar1220f-s
huaweiar150 firmware
huaweiar158evw
huaweiar160 firmware
huaweiar161
huaweiar161ew

and 41 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • 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

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.

  • Huawei AR1200, AR1200-S, AR150, AR160, AR200, AR2200, AR2200-S, AR3200, SRG1300, SRG2300, SRG3300

    • AR150 V200R010C00, AR160 V200R007C00, AR1200 V200R008C50, AR1200 V200R009C00, AR1200 V200R010C00, AR1200-S V200R007C00, AR1200-S V200R008C20, AR1200-S V200R008C50, AR1200-S V200R009C00, AR1200-S V200R010C00, AR150 V200R007C00, AR150 V200R008C20 … (+5)affected

Same product

huawei: all records

Other highest-scoring records for the same primary product.

  • CVE-2018-7920Huawei AR1200 V200R006C10SPC300, AR160 V200R006C10SPC300, AR200 V200R006C10SPC300, AR2200 V200R006C10SPC300, AR3200 V200R006C10SPC300 device
    30Monitor

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.

EPSS, last 120 days

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 researchers

Finders, 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).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • Administrator privileges are required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-347 · Improper Verification of Cryptographic Signature

CVSS vector

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

nvd-primary

Root cause

The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.

The bug in code

The whole CWE-347 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const claims = jwt.verify(token, publicKey);

Fixed

ts
const claims = jwt.verify(token, publicKey, {  algorithms: ["RS256"],  issuer: "https://id.example.com",  audience: "portal",});

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

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.

All records