dbcve.org
Rh1288 V3 Server FirmwareOperating system · Huawei

CVE-2016-6825

CRITICAL · 9.8 CVSS v3.0 Published 2016-09-07
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
Huawei XH620 V3, XH622 V3, and XH628 V3 servers with software before V100R003C00SPC610, RH1288 V3 servers with software before V100R003C00SPC613, RH2288 V3 servers with software before V100R003C00SPC617, and RH2288H V3 servers with software before V100R003C00SPC515 allow remote attackers to obtain passwords via a brute-force attack, related to "lack of authentication protection mechanisms."

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

Multiple Huawei server models (XH620 V3, XH622 V3, XH628 V3, RH1288 V3, RH2288 V3, RH2288H V3) have a critical authentication bypass vulnerability where lack of authentication protection mechanisms allows remote attackers to perform brute-force password attacks without any lockout, rate limiting, or account lockout protections.

MitigationApply vendor-supplied firmware/software patches (V100R003C00SPC610, SPC613, SPC617, or SPC515 depending on model) and implement compensating controls such as network-based rate limiting, account lockout policies, and network segmentation to reduce exposure until patching is complete.

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
Rh1288 V3 Server FirmwareOperating system
Affected:= v100r003c00
Rh2288 V3 Server FirmwareOperating system
Affected:= v100r003c00
Rh2288h V3 Server FirmwareOperating system
Affected:= v100r003c00
Xh620 V3 Server FirmwareOperating system
Affected:= v100r003c00
Xh622 V3 Server FirmwareOperating system
Affected:= v100r003c00
Xh628 V3 Server FirmwareOperating system
Affected:= v100r003c00

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 Huawei server model
    Check the server hardware label, BIOS, or iBMC/LOM web interface for the exact model number (XH620 V3, XH622 V3, XH628 V3, RH1288 V3, RH2288 V3, or RH2288H V3)
    Affected if The server model matches one of the six affected models listed in the CVE
  2. Check firmware version
    Access the iBMC or BIOS interface and navigate to the firmware version information section, or run the command 'ipmcget -t version' via IPMI if available
    Affected if The firmware version is exactly v100r003c00
  3. Verify iBMC web interface is accessible
    Attempt to access the server management web interface on the BMC IP address (typically ports 443 or 80) from a network location
    Affected if The iBMC web management interface is reachable from untrusted networks
  4. Test for account lockout protection
    Send multiple failed login attempts (5-10) to the iBMC web login endpoint using a script or manual testing tool
    Affected if There is no account lockout or temporary lockout after multiple failed attempts (no rate limiting or CAPTCHA)

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

Apply vendor-supplied firmware/software patches (V100R003C00SPC610, SPC613, SPC617, or SPC515 depending on model) and implement compensating controls such as network-based rate limiting, account lockout policies, and network segmentation to reduce exposure until patching is complete.

Recommended fix High confidence

V100R003C00SPC610 (XH620/622/628 V3), V100R003C00SPC613 (RH1288 V3), V100R003C00SPC617 (RH2288 V3), V100R003C00SPC515 (RH2288H V3) or later

  1. 1. Identify the exact server model (Rh1288 V3, Rh2288 V3, Rh2288H V3, Xh620 V3, Xh622 V3, or Xh628 V3) from the affected hardware inventory
  2. 2. Check the current firmware version installed on the affected server
  3. 3. Download the appropriate fixed firmware version from Huawei's official support website: V100R003C00SPC610 or later for XH620 V3/XH622 V3/XH628 V3; V100R003C00SPC613 or later for RH1288 V3; V100R003C00SPC617 or later for RH2288 V3; V100R003C00SPC515 or later for RH2288H V3
  4. 4. Review Huawei's firmware update instructions and ensure proper backup of current configuration
  5. 5. Apply the firmware update following Huawei's standard firmware upgrade procedure for the specific server model
  6. 6. After upgrade, verify the new firmware version is installed correctly
  7. 7. Confirm the authentication protection mechanism is now in place
Caveat Firmware upgrades may require downtime and should be tested in a staging environment before production deployment; ensure compatible BIOS and iBMC firmware versions

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

Fix this in Rh1288 V3 Server Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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