cve.bz

CVE-2017-17166 huawei: Uncontrolled Resource Consumption

5.3 mediumEPSS 1.3%

Medium (5.3) in huawei. EPSS 1.3% estimated probability of exploitation activity in the next 30 days.

On this page
Huawei DP300 V500R002C00, Secospace USG6300 V500R001C00, V500R001C20, V500R001C30, V500R001C50, Secospace USG6500 V500R001C00, V500R001C20, V500R001C30, V500R001C50, Secospace USG6600 V500R001C00, V500R001C20, V500R001C30, V500R001C50, TP3206 V100R002C00, VP9660 V500R002C00, V500R002C10 have a resource exhaustion vulnerability. The software does not process certain field of H.323 message properly, a remote unauthenticated attacker could send crafted H.323 message to the device, successful exploit could cause certain service unavailable since the stack memory is exhausted.

Severity

CVSS 3.0

5.3 medium
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
1.3% (unchanged from 1.3% a week ago; 1.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 70th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-400 Uncontrolled Resource Consumption
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-17166 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-17166?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-17166?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-17166 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
huawei:dp300_firmwarev500r002c00
huawei:secospace_usg6300_firmwarev500r001c00
huawei:secospace_usg6300_firmwarev500r001c20
huawei:secospace_usg6300_firmwarev500r001c30
huawei:secospace_usg6300_firmwarev500r001c50
huawei:secospace_usg6500_firmwarev500r001c00
huawei:secospace_usg6500_firmwarev500r001c20
huawei:secospace_usg6500_firmwarev500r001c30
huawei:secospace_usg6500_firmwarev500r001c50
huawei:secospace_usg6600_firmwarev500r001c00
huawei:secospace_usg6600_firmwarev500r001c20
huawei:secospace_usg6600_firmwarev500r001c30
huawei:secospace_usg6600_firmwarev500r001c50
huawei:tp3206_firmwarev100r002c00
huawei:vp9660_firmwarev500r002c00
huawei:vp9660_firmwarev500r002c10

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON