cve.bz

CVE-2017-17131 huawei: Infinite Loop

5.7 mediumEPSS 0.8%

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

On this page
Huawei DP300 V500R002C00; RP200 V500R002C00; V600R006C00; TE30 V100R001C10; V600R006C00; TE50 V600R006C00; TE60 V100R001C10; V500R002C00; V600R006C00; VP9660 V500R002C10 have an DoS vulnerability due to insufficient validation of the parameter when a putty comment key is loaded. An authenticated remote attacker can place a malformed putty key file in system when a system manager load the key an infinite loop happens which lead to reboot the system.

Severity

CVSS 3.0

5.7 medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
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-17131 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-17131?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-17131?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-17131 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:rp200_firmwarev500r002c00
huawei:rp200_firmwarev600r006c00
huawei:te30_firmwarev100r001c10
huawei:te30_firmwarev600r006c00
huawei:te50_firmwarev600r006c00
huawei:te60_firmwarev100r001c10
huawei:te60_firmwarev500r002c00
huawei:te60_firmwarev600r006c00
huawei:vp9660_firmwarev500r002c10

References

Check your stackJSON