dbcve.org
Espace 7910 FirmwareOperating system · Huawei

CVE-2017-17223

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
Remotely reachable 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 eSpace 7910 V200R003C30; eSpace 7950 V200R003C30; eSpace 8950 V200R003C00; V200R003C30 have a directory traversal vulnerability. An authenticated, remote attacker can craft specific URL to the affected products. Due to insufficient verification of the URL, successful exploit will upload and download files and cause information leak and system crash.

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

Directory traversal vulnerability in Huawei eSpace IP phone firmware (7910, 7950, 8950 V200R003Cxx). Authenticated remote attackers can craft malicious URLs to traverse filesystem directories, enabling unauthorized file upload/download, information disclosure, and potential system crash.

MitigationApply vendor-supplied patches for affected V200R003Cxx versions; implement strict URL path validation and restrict file system access permissions to prevent unauthorized directory traversal.

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
Espace 7910 FirmwareOperating system
Affected:= v200r003c30
Espace 7950 FirmwareOperating system
Affected:= v200r003c30
Espace 8950 FirmwareOperating system
Affected:= v200r003c00= v200r003c30

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

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 device model and firmware version
    Access the device web interface or use SNMP to query the device. For web interface, log in and navigate to the system information or about page. For command line, access via Telnet/SSH and run 'show system-info' or similar command to retrieve the firmware version.
    Affected if The device model is 7910, 7950, or 8950 AND the firmware version is exactly v200r003c30 (for 7910/7950) or exactly v200r003c00 or v200r003c30 (for 8950)
  2. Verify web management interface is enabled
    Check if the device HTTP/HTTPS web management interface is accessible by attempting to reach the device IP on ports 80 or 443. Use a browser or curl command: curl -k http://<device-ip>/ or https://<device-ip>/
    Affected if The web interface responds, indicating it is enabled and accessible on the network
  3. Confirm authentication is required for the web interface
    Attempt to access protected pages on the web interface without credentials. Observe whether the device redirects to a login page or returns a 401/403 authentication error.
    Affected if The web interface requires authentication (login page appears), meaning the vulnerability is present in the authentication flow
  4. Check for signs of directory traversal exploitation
    Review web server access logs for suspicious patterns such as '../' sequences in URLs, unusual file access attempts, or access to system configuration files. Example suspicious requests: /../../etc/passwd or /../../etc/config
    Affected if Logs show URL patterns with directory traversal sequences or unauthorized access to system files outside the web root

The device is affected if it is a Huawei eSpace 7910, 7950, or 8950 running exactly the specified vulnerable firmware versions (v200r003c00 or v200r003c30) and has its web management interface enabled and accessible.

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-supplied patches for affected V200R003Cxx versions; implement strict URL path validation and restrict file system access permissions to prevent unauthorized directory traversal.

Fix this in Espace 7910 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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