dbcve.org
Ar1200 FirmwareOperating system · Huawei

CVE-2019-5300

MEDIUM · 6.7 CVSS v3.0 Published 2019-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This vulnerability allows a local attacker with high privilege to bypass digital signature verification for firmware images on Huawei AR and SRG router series. The affected software improperly verifies digital signatures, enabling installation of tampered or malicious firmware that bypasses integrity checks.

MitigationApply vendor-supplied firmware patches or updates for the affected router models (AR1200, AR1200-S, AR150, AR160, AR200, AR2200, AR2200-S, AR3200, SRG1300, SRG2300, SRG3300) that properly implement digital signature verification.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ar1200 FirmwareOperating system
Affected:= v200r007c00= v200r008c20= v200r008c50= v200r009c00= v200r010c00
Ar1200 S FirmwareOperating system
Affected:= v200r007c00= v200r008c20= v200r008c50= v200r009c00= v200r010c00
Ar150 FirmwareOperating system
Affected:= v200r007c00= v200r008c20= v200r008c50= v200r009c00= v200r010c00
Ar160 FirmwareOperating system
Affected:= v200r007c00= v200r008c20= v200r008c50= v200r009c00= v200r010c00
Ar200 FirmwareOperating system
Affected:= v200r007c00= v200r008c20= v200r008c50= v200r009c00= v200r010c00
Ar2200 FirmwareOperating system
Affected:= v200r007c00= v200r008c20= v200r008c50= v200r009c00= v200r010c00
Ar2200s FirmwareOperating system
Affected:= v200r007c00= v200r008c20= v200r008c50= v200r009c00= v200r010c00
Ar3200 FirmwareOperating system
Affected:= v200r007c00= v200r008c20= v200r008c50= v200r009c00= v200r010c00

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Execute 'display device' or 'display version' command in the device CLI to retrieve the hardware model information
    Affected if The device model is one of: AR1200, AR1200-S, AR150, AR160, AR200, AR2200, AR2200-S, or AR3200 series routers
  2. Retrieve firmware version
    Execute 'display version' command in the device CLI to obtain the installed firmware version string
    Affected if The firmware version matches exactly: v200r007c00, v200r008c20, v200r008c50, v200r009c00, or v200r010c00
  3. Verify signature verification capability
    Check system security settings by examining the boot system configuration and digital signature verification status using 'display secureboot status' or reviewing startup configuration files
    Affected if Digital signature verification for firmware is disabled or not enforced in the current boot configuration
  4. Confirm upgrade mechanism availability
    Examine if the device allows firmware upgrade or boot image change via 'display boot-loader' or by reviewing the startup configuration for boot system commands
    Affected if The device permits loading or upgrading firmware without requiring cryptographic signature validation

The device is affected if it is an AR series router (AR1200/AR1200-S/AR150/AR160/AR200/AR2200/AR2200-S/AR3200) running any of the specific versions v200r007c00, v200r008c20, v200r008c50, v200r009c00, or v200r010c00 and the digital signature verification for firmware is not properly enforced.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware patches or updates for the affected router models (AR1200, AR1200-S, AR150, AR160, AR200, AR2200, AR2200-S, AR3200, SRG1300, SRG2300, SRG3300) that properly implement digital signature verification.

Fix this in Ar1200 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5300 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-5300 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data