dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-17137

MEDIUM · 5.5 CVSS v3.0 Published 2018-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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
PEM module of Huawei DP300 V500R002C00; IPS Module V500R001C00; V500R001C30; NGFW Module V500R001C00; V500R002C00; NIP6300 V500R001C00; V500R001C30; NIP6600 V500R001C00; V500R001C30; RP200 V500R002C00; V600R006C00; S12700 V200R007C00; V200R007C01; V200R008C00; V200R009C00; V200R010C00; S1700 V200R006C10; V200R009C00; V200R010C00; S2700 V200R006C10; V200R007C00; V200R008C00; V200R009C00; V200R010C00; S5700 V200R006C00; V200R007C00; V200R008C00; V200R009C00; V200R010C00; S6700 V200R008C00; V200R009C00; V200R010C00; S7700 V200R007C00; V200R008C00; V200R009C00; V200R010C00; S9700 V200R007C00; V200R007C01; V200R008C00; V200R009C00; V200R010C00; Secospace USG6300 V500R001C00; V500R001C30; Secospace USG6500 V500R001C00; V500R001C30; Secospace USG6600 V500R001C00; V500R001C30S; TE30 V100R001C02; V100R001C10; V500R002C00; V600R006C00; TE40 V500R002C00; V600R006C00; TE50 V500R002C00; V600R006C00; TE60 V100R001C01; V100R001C10; V500R002C00; V600R006C00; TP3106 V100R002C00; TP3206 V100R002C00; V100R002C10; USG9500 V500R001C00; V500R001C30; ViewPoint 9030 V100R011C02; V100R011C03 has an Out-of-Bounds memory access vulnerability due to insufficient verification. An authenticated local attacker can make processing crash by a malicious certificate. The attacker can exploit this vulnerability to cause a denial of service.

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 PEM (Privacy-Enhanced Mail) certificate parsing module in affected Huawei products contains an out-of-bounds memory access vulnerability caused by insufficient verification of certificate data. An authenticated local attacker can craft a malicious certificate that triggers the vulnerability, causing the processing to crash and resulting in denial of service.

MitigationApply vendor-provided patches for the affected product versions. In the interim, restrict local access to trusted authenticated users only and validate that any certificates loaded into the system originate from trusted sources.

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
Ips Module FirmwareOperating system
Affected:= v500r001c00= v500r001c30
Ngfw Module FirmwareOperating system
Affected:= v500r001c00= v500r002c00
Nip6300 FirmwareOperating system
Affected:= v500r001c00= v500r001c30
Nip6600 FirmwareOperating system
Affected:= v500r001c00= v500r001c30
Rp200 FirmwareOperating system
Affected:= v500r002c00= v600r006c00
S12700 FirmwareOperating system
Affected:= v200r007c00= v200r007c01= v200r008c00= v200r009c00= v200r010c00
S1700 FirmwareOperating system
Affected:= v200r006c10= v200r009c00= v200r010c00

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

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 the Huawei product model
    Locate the product label or access the device management interface to determine the exact model (Dp300, Ips Module, Ngfw Module, Nip6300, Nip6600, Rp200, S12700, or S1700)
    Affected if The model is one of the affected products listed in the CVE
  2. Check the installed firmware version
    Access the device command line or management interface and run the command to display firmware version (typically 'display version' or check in system info menu)
    Affected if The firmware version exactly matches any of these: v500r002c00, v500r001c00, v500r001c30, v500r002c00, v600r006c00, v200r007c00, v200r007c01, v200r008c00, v200r009c00, v200r010c00, v200r006c10
  3. Verify if PEM certificate parsing is in use
    Check system configuration for loaded certificates or examine SSL/TLS settings that reference PEM-formatted certificates
    Affected if The system is configured to parse or load PEM-format certificates
  4. Confirm local authenticated access scope
    Review user accounts with local access privileges and examine access control lists for the management interface
    Affected if Multiple authenticated users exist or the system permits local authentication access beyond a single trusted administrator

The environment is affected if the product model matches one of the eight affected Huawei products AND the installed firmware version exactly matches a listed vulnerable version AND the system uses PEM certificate parsing with local authentication access.

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

Apply vendor-provided patches for the affected product versions. In the interim, restrict local access to trusted authenticated users only and validate that any certificates loaded into the system originate from trusted sources.

Fix this in Dp300 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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