dbcve.org
Dp300 FirmwareOperating system · Huawei

CVE-2017-2722

HIGH · 8.8 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 →
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
DP300 V500R002C00,TE60 with software V100R001C01, V100R001C10, V100R003C00, V500R002C00 and V600R006C00,TP3106 with software V100R001C06 and V100R002C00,ViewPoint 9030 with software V100R011C02, V100R011C03,eCNS210_TD with software V100R004C10,eSpace 7950 with software V200R003C00 and V200R003C30,eSpace IAD with software V300R001C07SPCa00 and V300R002C01SPCb00,eSpace U1981 with software V100R001C20, V100R001C30, V200R003C00, V200R003C20 and V200R003C30 have an input validation vulnerability.A remote attacker may exploit this vulnerability by crafting a malformed packet and sending it to the device. A successful exploit could allow the attacker to cause a denial of service or execute arbitrary code.

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 · moderate confidence

This is an input validation vulnerability affecting multiple Huawei video conferencing and communication devices (DP300, TE60, TP3106, ViewPoint 9030, eCNS210_TD, eSpace series, eSpace IAD, eSpace U1981). A remote attacker can exploit this by sending malformed packets to the device, potentially causing denial of service or executing arbitrary code due to improper validation of input data.

MitigationApply the vendor-supplied firmware updates for the specific affected versions listed in the Huawei security advisory. Until patches are applied, consider network segmentation and filtering to limit exposure to untrusted network paths.

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
Te60 FirmwareOperating system
Affected:= v100r001c01= v100r001c10= v100r003c00= v500r002c00= v600r006c00
Tp3106 FirmwareOperating system
Affected:= v100r001c06= v100r002c00
Viewpoint 9030 FirmwareOperating system
Affected:= v100r011c02= v100r011c03
Ecns210 Td FirmwareOperating system
Affected:= v100r004c10
Espace 7950 FirmwareOperating system
Affected:= v200r003c00= v200r003c30
Espace Iad FirmwareOperating system
Affected:= v300r001c07spca00= v300r002c01spcb00
Espace U1981 FirmwareOperating system
Affected:= v100r001c20= v100r001c30= v200r003c00= 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
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 affected Huawei devices in your environment
    Inventory all Huawei devices on the network, specifically looking for: DP300, TE60, TP3106, ViewPoint 9030, eCNS210_TD, eSpace 7950, eSpace IAD, and eSpace U1981. Use network scans or asset management tools to locate these devices.
    Affected if Any of these specific model numbers are present in the environment
  2. Check firmware version on DP300 devices
    Access the device management interface or use SNMP/CLI to retrieve the firmware version. For DP300, look for version v500r002c00.
    Affected if Firmware version equals v500r002c00
  3. Check firmware version on TE60 devices
    Access the device management interface or use SNMP/CLI to retrieve the firmware version. For TE60, look for versions v100r001c01, v100r001c10, v100r003c00, v500r002c00, or v600r006c00.
    Affected if Firmware version equals any of: v100r001c01, v100r001c10, v100r003c00, v500r002c00, or v600r006c00
  4. Check firmware version on TP3106 and ViewPoint 9030 devices
    Access the device management interface or use SNMP/CLI to retrieve the firmware version. For TP3106 look for v100r001c06 or v100r002c00. For ViewPoint 9030 look for v100r011c02 or v100r011c03.
    Affected if TP3106 firmware is v100r001c06 or v100r002c00; OR ViewPoint 9030 firmware is v100r011c02 or v100r011c03
  5. Check firmware version on eSpace and eCNS210_TD devices
    Access the device management interface or use SNMP/CLI to retrieve the firmware version. eSpace 7950: v200r003c00 or v200r003c30. eSpace IAD: v300r001c07spca00 or v300r002c01spcb00. eSpace U1981: v100r001c20, v100r001c30, v200r003c00, v200r003c20, or v200r003c30. eCNS210_TD: v100r004c10.
    Affected if Any eSpace or eCNS210_TD device matches the specific versions listed above

You are affected if any Huawei DP300, TE60, TP3106, ViewPoint 9030, eCNS210_TD, eSpace 7950, eSpace IAD, or eSpace U1981 devices in your environment run exactly one of the firmware versions enumerated in the CVE advisory.

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 the vendor-supplied firmware updates for the specific affected versions listed in the Huawei security advisory. Until patches are applied, consider network segmentation and filtering to limit exposure to untrusted network paths.

Fix this in Dp300 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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