dbcve.org
Rh1288 V3 Server FirmwareOperating system · Huawei

CVE-2016-6838

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 X6800 and XH620 V3 servers with software before V100R003C00SPC606, RH1288 V3 servers with software before V100R003C00SPC613, RH2288 V3 servers with software before V100R003C00SPC617, CH140 V3 and CH226 V3 servers with software before V100R001C00SPC122, CH220 V3 servers with software before V100R001C00SPC201, and CH121 V3 and CH222 V3 servers with software before V100R001C00SPC202 might allow remote attackers to decrypt encrypted data and consequently obtain sensitive information by leveraging selection of an insecure SSH encryption algorithm.

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

Huawei server models run SSH with insecure encryption algorithm selection, allowing remote attackers to decrypt SSH sessions and obtain sensitive information. The vulnerability stems from support for weak ciphers, MAC algorithms, or key exchange methods in the SSH configuration.

MitigationUpdate firmware/software to the patched versions (V100R003C00SPC606 or later for X6800/XH620 V3, V100R003C00SPC613 or later for RH1288 V3, V100R003C00SPC617 or later for RH2288 V3, V100R001C00SPC122 or later for CH140 V3/CH226 V3, V100R001C00SPC201 or later for CH220 V3, V100R001C00SPC202 or later for CH121 V3/CH222 V3) and configure SSH to use only strong encryption algorithms.

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
X6800 V3 Server FirmwareOperating system
Affected:= v100r003c00
Xh620 V3 Server FirmwareOperating system
Affected:= v100r003c00
Ch121 V3 Server FirmwareOperating system
Affected:= v100r001c00
Ch140 V3 Server FirmwareOperating system
Affected:= v100r001c00
Ch220 V3 Server FirmwareOperating system
Affected:= v100r001c00
Ch222 V3 Server FirmwareOperating system
Affected:= v100r001c00

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
None
Availability
None

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

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 server model
    Check the server model label on the physical server or access the iBMC/BMC web interface to confirm the exact model (Rh1288 V3, Rh2288 V3, X6800 V3, Xh620 V3, Ch121 V3, Ch140 V3, Ch220 V3, or Ch222 V3)
    Affected if The server model matches one of the affected models listed in the CVE
  2. Check the current firmware version
    Access the iBMC/BMC management interface or use the command line tool to query the firmware version (for example, through the 'ipmcget -v' or similar BMC command). Compare the version number against the affected versions (v100r003c00 for Rh1288 V3/Rh2288 V3/X6800 V3/Xh620 V3, v100r001c00 for Ch121 V3/Ch140 V3/Ch220 V3/Ch222 V3)
    Affected if The installed firmware version exactly matches v100r003c00 or v100r001c00 for the respective model
  3. Verify SSH service is enabled and accessible
    Confirm that SSH service is running on the server (check if port 22 is open and responding, or check the iBMC SSH service status)
    Affected if SSH is enabled and reachable on the management interface
  4. Inspect SSH configuration for weak algorithms
    If you have CLI access to the BMC/iBMC or can view the SSH daemon configuration, examine the SSH configuration files or running config for supported ciphers, MAC algorithms, and key exchange methods. Look for weak or deprecated options such as 3des-cbc, blowfish-cbc, aes128-cbc, hmac-md5, hmac-sha1, or diffie-hellman-group1-sha1
    Affected if The SSH configuration includes any weak ciphers (such as CBC-based ciphers), weak MAC algorithms (such as MD5 or SHA1), or weak key exchange methods (such as group1)

A user is affected if they are running one of the listed Huawei server models with the specific firmware version (v100r003c00 or v100r001c00) and have SSH enabled with weak encryption algorithms configured.

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

Update firmware/software to the patched versions (V100R003C00SPC606 or later for X6800/XH620 V3, V100R003C00SPC613 or later for RH1288 V3, V100R003C00SPC617 or later for RH2288 V3, V100R001C00SPC122 or later for CH140 V3/CH226 V3, V100R001C00SPC201 or later for CH220 V3, V100R001C00SPC202 or later for CH121 V3/CH222 V3) and configure SSH to use only strong encryption algorithms.

Fix this in Rh1288 V3 Server 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-2016-6838 — 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-6838 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