dbcve.org
Usg2100Application · Huawei

CVE-2016-8276

CRITICAL · 9.8 CVSS v3.0 Published 2016-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 Point-to-Point Protocol over Ethernet (PPPoE) module in Huawei USG2100, USG2200, USG5100, and USG5500 unified security gateways with software before V300R001C10SPC600, when CHAP authentication is configured on the server, allows remote attackers to cause a denial of service (server restart) or execute arbitrary code via crafted packets sent during authentication.

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 vulnerability in the PPPoE module of Huawei USG2100, USG2200, USG5100, and USG5500 unified security gateways. When CHAP authentication is enabled on the PPPoE server, specially crafted packets sent during the authentication handshake can overflow a buffer, enabling remote code execution or causing device denial of service via restart.

MitigationUpdate affected devices to software version V300R001C10SPC600 or later. If immediate patching is not feasible, consider disabling CHAP authentication on PPPoE servers or implementing network access controls to limit PPPoE exposure to trusted sources.

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
Usg2100Application
Affected:= v300r001c00= v300r001c10
Usg2200Application
Affected:= v300r001c00= v300r001c10
Usg5100Application
Affected:= v300r001c00= v300r001c10
Usg5500Application
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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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
    Check the hardware model of the Huawei unified security gateway (USG2100, USG2200, USG5100, or USG5500) via the device console, web interface, or command 'display device'
    Affected if The device is a USG2100, USG2200, USG5100, or USG5500 model
  2. Check the installed firmware version
    Run the command 'display version' or check the system software version in the web interface to identify the exact firmware version
    Affected if The firmware version is exactly v300r001c00 or v300r001c10
  3. Verify PPPoE server configuration
    Run the command 'display pppoe-server configuration' or check the PPPoE server settings in the web interface under PPPoE configuration
    Affected if A PPPoE server is configured and active on the device
  4. Confirm CHAP authentication is enabled
    In the PPPoE server settings, verify whether CHAP (Challenge Handshake Authentication Protocol) authentication is enabled for PPPoE connections
    Affected if CHAP authentication is enabled on the PPPoE server configuration

The device is affected if it is a USG2100/USG2200/USG5100/USG5500 running firmware v300r001c00 or v300r001c10 AND has a PPPoE server with CHAP authentication enabled.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected devices to software version V300R001C10SPC600 or later. If immediate patching is not feasible, consider disabling CHAP authentication on PPPoE servers or implementing network access controls to limit PPPoE exposure to trusted sources.

Recommended fix Moderate confidence

V300R001C10SPC600

  1. 1. Access the USG device console or web management interface
  2. 2. Navigate to System > Maintenance > Upgrade to check current software version
  3. 3. Verify current version is before V300R001C10SPC600 (v300r001c00 or v300r001c10 are affected)
  4. 4. Download the V300R001C10SPC600 or later firmware from Huawei official support website (support.huawei.com)
  5. 5. Backup current configuration via System > Configuration > Backup or console command 'display current-configuration'
  6. 6. Upload the new firmware file through the management interface or via FTP/TFTP to the device
  7. 7. Initiate the upgrade and wait for completion - do not power off during the process
  8. 8. After reboot, verify new version via 'display version' command

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Usg2100 Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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