CVE intelligence and bounded remediation

CVE-2015-7843 — Huawei Fusionserver Ch121 V3 security vulnerability

High CVSS 8.8

The management interface on Huawei FusionServer rack servers RH2288 V3 with software before V100R003C00SPC603, RH2288H V3 with software before V100R003C00SPC503, XH628 V3 with software before V100R003C00SPC602, RH1288 V3 with software before V100R003C00SPC602, RH2288A V2 with software before V100R002C00SPC701, RH1288A V2 with software before V100R002C00SPC502, RH8100 V3 with software before V100R003C00SPC110, CH222 V3 with software before V100R001C00SPC161, CH220 V3 with software before V100R001C00SPC161, and CH121 V3 with software before V100R001C00SPC161 does not limit the number of query attempts, which allows remote authenticated users to obtain credentials of higher-level users via a brute force attack.

Severity
High
CVSS
8.8 (3.0)
Published
2017-10-03
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-254

Affected products

  • huawei / fusionserver_ch121_v3 / v100r001c00
  • huawei / fusionserver_ch220_v3 / v100r001c00
  • huawei / fusionserver_ch222_v3 / v100r001c00
  • huawei / fusionserver_rh1288_v3 / v100r003c00spc100
  • huawei / fusionserver_rh1288a_v2 / v100r002c00
  • huawei / fusionserver_rh2288_v3 / v100r003c00

Showing 6 representative product identities from 10 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

General vulnerability remediation

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Confirm the affected component, deployment paths, reachable interfaces, and enabled features from inventories and configuration, without probing production destructively.
  • Compare the advisory's affected conditions with the repository lockfiles, build manifests, artifacts, and runtime inventory.
  • Identify data sensitivity, trust boundaries, and privilege level for every confirmed affected deployment.

Remediate safely

  • Apply a vendor-supported fix or remove the affected component or feature; record the selected change and its source in the repository.
  • Update direct and transitive dependency locks, generated artifacts, deployment manifests, and asset inventories together.
  • Add a regression test for the documented unsafe condition using inert inputs and preserve rollback instructions.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.