dbcve.org
Softco FirmwareOperating system · Huawei

CVE-2017-2690

MEDIUM · 5.5 CVSS v3.0 Published 2017-11-22
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
SoftCo with software V200R003C20,eSpace U1910 with software V200R003C00, V200R003C20 and V200R003C30,eSpace U1911 with software V200R003C20, V200R003C30,eSpace U1930 with software V200R003C20 and V200R003C30,eSpace U1960 with software V200R003C20, V200R003C30,eSpace U1980 with software V200R003C20, V200R003C30,eSpace U1981 with software V200R003C20 and V200R003C30 have an denial of service (DoS) vulnerability, which allow an attacker with specific permission to craft a file containing malicious data and upload it to the device to exhaust memory, causing a DoS condition.

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

This is an authenticated denial of service vulnerability in Huawei eSpace/SoftCo unified communications devices. An attacker with specific permissions can upload a specially crafted file containing malicious data to the device, which causes memory exhaustion and leads to a DoS condition. The vulnerability affects multiple eSpace models and SoftCo running specific software versions (V200R003C00-C30).

MitigationApply vendor patches for the affected software versions. Implement file upload validation, memory limits, and monitoring for anomalous file uploads to mitigate exploitation while patching.

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
Softco FirmwareOperating system
Affected:= v200r003c20
Espace U1910 FirmwareOperating system
Affected:= v200r003c00= v200r003c20= v200r003c30
Espace U1911 FirmwareOperating system
Affected:= v200r003c20= v200r003c30
Espace U1930 FirmwareOperating system
Affected:= v200r003c20= v200r003c30
Espace U1960 FirmwareOperating system
Affected:= v200r003c20= v200r003c30
Espace U1980 FirmwareOperating system
Affected:= v200r003c20= v200r003c30
Espace U1981 FirmwareOperating system
Affected:= v200r003c20= 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
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 device model and firmware version
    Access the device management console or use CLI command 'display version' to identify the exact model (SoftCo, U1910, U1911, U1930, U1960, U1980, or U1981) and firmware version string.
    Affected if The device model is any of the affected eSpace models or SoftCo and the firmware version is v200r003c00, v200r003c20, or v200r003c30.
  2. Confirm file upload feature is accessible
    Check if the device has the file upload functionality enabled. In Huawei eSpace/SoftCo, this is typically found in the management web interface under file management or backup/restore settings, or via CLI command related to file transfer.
    Affected if The file upload feature is available to the authenticated user with the specific permissions required for this attack.
  3. Verify user has the required privilege level
    Review the user account privileges using 'display user' or similar administrative command to determine if the account has file upload permissions.
    Affected if The authenticated user account possesses the specific permissions that allow file upload operations.
  4. Check for memory exhaustion indicators
    Monitor device memory usage via 'display memory-usage' CLI command or through the management interface. Look for abnormally high memory consumption or service degradation.
    Affected if Memory usage is critically high or the device is experiencing service instability consistent with memory exhaustion.

The device is affected if it is a Huawei eSpace model (U1910, U1911, U1930, U1960, U1980, U1981) or SoftCo running firmware version v200r003c00, v200r003c20, or v200r003c30, with an authenticated user who has file upload permissions.

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 patches for the affected software versions. Implement file upload validation, memory limits, and monitoring for anomalous file uploads to mitigate exploitation while patching.

Fix this in Softco Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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