CVE intelligence and bounded remediation

CVE-2017-17174 — Huawei Rse6500 Firmware security vulnerability

Medium CVSS 5.9

Some Huawei products RSE6500 V500R002C00; SoftCo V200R003C20SPCb00; VP9660 V600R006C10; eSpace U1981 V100R001C20; V200R003C20; V200R003C30; V200R003C50 have a weak algorithm vulnerability. To exploit the vulnerability, a remote, unauthenticated attacker has to capture TLS traffic between clients and the affected products. The attacker may launch the Bleichenbacher attack on RSA key exchange to decrypt the session key and the previously captured sessions by some cryptanalytic operations. Successful exploit may cause information leak.

Severity
Medium
CVSS
5.9 (3.0)
Published
2018-07-31
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-310

Affected products

  • huawei / rse6500_firmware / v500r002c00
  • huawei / softco_firmware / v200r003c20spcb00
  • huawei / vp9660_firmware / v600r006c10
  • huawei / espace_u1981_firmware / v200r001c20
  • huawei / espace_u1981_firmware / v200r003c20
  • huawei / espace_u1981_firmware / v200r003c30

Showing 6 representative product identities from 7 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.