dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-17167

MEDIUM · 5.9 CVSS v3.0 Published 2018-03-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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 DP300 V500R002C00; TP3206 V100R002C00; ViewPoint 9030 V100R011C02; V100R011C03 have a use of a broken or risky cryptographic algorithm vulnerability. The software uses risky cryptographic algorithm in SSL. This is dangerous because a remote unauthenticated attacker could use well-known techniques to break the algorithm. Successful exploit could result in the exposure of sensitive information.

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

The affected Huawei products (DP300, TP3206, ViewPoint 9030) use broken or risky cryptographic algorithms in their SSL implementation. This allows a remote unauthenticated attacker to exploit well-known cryptographic weaknesses (such as weak ciphers, deprecated protocols like SSLv2/v3, or weak hashing algorithms) to potentially decrypt sensitive communications.

MitigationDisable weak cryptographic algorithms and deprecated SSL protocols in the SSL configuration, ensuring only strong ciphers and TLS 1.2+ protocols are enabled. Verify compatibility with legitimate clients after changes.

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
Dp300 FirmwareOperating system
Affected:= v500r002c00
Tp3206 FirmwareOperating system
Affected:= v100r002c00
Viewpoint 9030 FirmwareOperating system
Affected:= v100r011c02= v100r011c03

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:H/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 product model and firmware version
    Access the device management interface or use the command line to retrieve the product model and exact firmware version. For DP300, TP3206, and ViewPoint 9030, this is typically found in the system information or about section of the web management console.
    Affected if The device is a Huawei DP300 running v500r002c00, TP3206 running v100r002c00, or ViewPoint 9030 running v100r011c02 or v100r011c03.
  2. Locate SSL/TLS configuration settings
    In the device web management interface, navigate to the SSL/TLS or security settings section where encryption protocols and cipher suites are configured. This is usually under Network Settings, Security, or SSL Configuration menus.
    Affected if Weak or deprecated protocol options (SSLv2, SSLv3) are available or enabled in the configuration.
  3. Verify enabled SSL/TLS protocols
    Examine the protocol version options in the SSL configuration. Check if SSLv2, SSLv3, or early TLS versions (TLS 1.0, 1.1) are enabled.
    Affected if Any of SSLv2, SSLv3, TLS 1.0, or TLS 1.1 protocols are enabled on the device.
  4. Review configured cipher suites
    In the SSL configuration panel, review the list of enabled cipher suites. Look for cipher suites using weak hashing algorithms (MD5, SHA-1) or weak encryption (DES, 40-bit or 56-bit ciphers).
    Affected if Weak cipher suites such as those using NULL, EXPORT, DES, 3DES, MD5, or RC4 are enabled.
  5. Confirm vulnerability conditions
    Cross-reference the findings: the device must be both (1) running one of the specific affected firmware versions AND (2) have weak cryptographic algorithms or deprecated protocols enabled in the SSL configuration.
    Affected if The device runs an affected firmware version AND has weak ciphers, deprecated protocols, or weak hashing algorithms enabled in its SSL configuration.

You are affected if your Huawei DP300, TP3206, or ViewPoint 9030 device runs one of the listed vulnerable firmware versions AND has weak cryptographic algorithms or deprecated SSL protocols (SSLv2/v3) enabled in the SSL configuration.

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

Disable weak cryptographic algorithms and deprecated SSL protocols in the SSL configuration, ensuring only strong ciphers and TLS 1.2+ protocols are enabled. Verify compatibility with legitimate clients after changes.

Fix this in Dp300 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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