CVE-2017-17136: Buffer Overflow
PEM module of Huawei DP300 V500R002C00; IPS Module V500R001C00; V500R001C30; NGFW Module V500R001C00; V500R002C00; NIP6300 V500R001C00; V500R001C30; NIP6600 V500R001C00; V500R001C30; RP200 V500R002C00; V600R006C00; S12700 V200R007C00; V200R007C01; V200R008C00; V200R009C00; V200R010C00; S1700 V200R006C10; V200R009C00; V200R010C00; S2700 V200R006C10; V200R007C00; V200R008C00; V200R009C00; V200R010C00; S5700 V200R006C00; V200R007C00; V200R008C00; V200R009C00; V200R010C00; S6700 V200R008C00; V200R009C00; V200R010C00; S7700 V200R007C00; V200R008C00; V200R009C00; V200R010C00; S9700 V200R007C00; V200R007C01; V200R008C00; V200R009C00; V200R010C00; Secospace USG6300 V500R001C00; V500R001C30; Secospace USG6500 V500R001C00; V500R001C30; Secospace USG6600 V500R001C00; V500R001C30S; TE30 V100R001C02; V100R001C10; V500R002C00; V600R006C00; TE40 V500R002C00; V600R006C00; TE50 V500R002C00; V600R006C00; TE60 V100R001C01; V100R001C10; V500R002C00; V600R006C00; TP3106 V100R002C00; TP3206 V100R002C00; V100R002C10; USG9500 V500R001C00; V500R001C30; ViewPoint 9030 V100R011C02; V100R011C03 has a heap overflow vulnerability due to insufficient verification. An authenticated local attacker can make processing crash by a malicious certificate. The attacker can exploit this vulnerability to cause a denial of service.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-17136?
CVE-2017-17136 has been rated as a high severity vulnerability due to its impact on the confidentiality and integrity of the affected devices.
How do I fix CVE-2017-17136?
To fix CVE-2017-17136, you should upgrade to the latest firmware version provided by Huawei as recommended in their security advisory.
What devices are affected by CVE-2017-17136?
CVE-2017-17136 affects various Huawei devices including the DP300, IPS Module, NGFW Module, NIP6300, and several others listed in the advisory.
Is there a workaround for CVE-2017-17136?
There are no specific workarounds available for CVE-2017-17136; updating the firmware is necessary to mitigate the vulnerability.
Has CVE-2017-17136 been exploited in the wild?
There are no reports indicating that CVE-2017-17136 has been actively exploited in the wild, but it is still classified as a critical vulnerability that requires prompt attention.