dbcve.org
Usg2100 FirmwareOperating system · Huawei

CVE-2016-6669

HIGH · 7.5 CVSS v3.0 Published 2016-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable 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
Buffer overflow in the Authentication, Authorization and Accounting (AAA) module in Huawei USG2100, USG2200, USG5100, and USG5500 unified security gateways with software before V300R001C10SPC600 allows remote authenticated RADIUS servers to execute arbitrary code by sending a crafted EAP packet.

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

Buffer overflow in the AAA (Authentication, Authorization and Accounting) module of Huawei USG2100, USG2200, USG5100, and USG5500 unified security gateways allows remote authenticated RADIUS servers to execute arbitrary code by sending a specially crafted EAP (Extensible Authentication Protocol) packet.

MitigationUpgrade Huawei USG firmware to version V300R001C10SPC600 or later to patch the vulnerability. If immediate upgrade is not feasible, restrict and monitor RADIUS server access to trusted sources only.

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
Usg2100 FirmwareOperating system
Affected:<= v300r001c00<= v300r001c10
Usg2200 FirmwareOperating system
Affected:<= v300r001c00<= v300r001c10
Usg5100 FirmwareOperating system
Affected:<= v300r001c00<= v300r001c10
Usg5500 FirmwareOperating system
Affected:<= v300r001c00<= v300r001c10

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
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:L/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 the device model
    Log into the USG device console or web interface and run 'display device' or check the system information to confirm the exact model (USG2100, USG2200, USG5100, or USG5500)
    Affected if The model is one of USG2100, USG2200, USG5100, or USG5500
  2. Check the installed firmware version
    Run 'display version' or check the firmware version in the device management interface. Note the full version string (e.g., v300r001c00, v300r001c10, etc.)
    Affected if The firmware version is v300r001c00 or v300r001c10 or any version lower than these (for example, earlier maintenance releases)
  3. Verify RADIUS authentication is enabled
    Run 'display radius scheme' or access the AAA configuration to check if RADIUS authentication is configured and active. The vulnerability exists in the AAA module handling RADIUS.
    Affected if RADIUS authentication is configured and enabled on the device
  4. Check if EAP is configured for RADIUS
    Run 'display radius scheme [scheme-name]' and look for EAP (Extensible Authentication Protocol) configuration settings within the RADIUS setup
    Affected if EAP authentication method is enabled or configured for the RADIUS scheme
  5. Review RADIUS server access control
    Run 'display radius server' or check the RADIUS server configuration to identify which servers are permitted to authenticate. The attacker must be an authenticated RADIUS server.
    Affected if RADIUS servers with write access or full authentication privileges are configured, especially from untrusted networks

The device is affected if it is a USG2100/USG2200/USG5100/USG5500 model running firmware v300r001c00 or v300r001c10 (or earlier) with RADIUS authentication and EAP enabled, allowing a remote authenticated RADIUS server to send specially crafted packets.

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

Upgrade Huawei USG firmware to version V300R001C10SPC600 or later to patch the vulnerability. If immediate upgrade is not feasible, restrict and monitor RADIUS server access to trusted sources only.

Fix this in Usg2100 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-6669 — 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-2016-6669 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