5.3
MEDIUM
CVE-2017-15332
Huawei AR, USG and Secospace Memory Leak Vulnerability in H323 Protocol
Description

Huawei AR120-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR1200 V200R006C10, V200R006C13, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR1200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR150 V200R006C10, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR150-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR160 V200R006C10, V200R006C12, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR200 V200R006C10, V200R007C00, V200R007C01, V200R008C20, V200R008C30, AR200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR2200 V200R006C10, V200R006C13, V200R006C16PWE, V200R007C00, V200R007C01, V200R007C02, V200R008C20, V200R008C30, AR2200-S V200R006C10, V200R007C00, V200R008C20, V200R008C30, AR3200 V200R006C10, V200R006C11, V200R007C00, V200R007C01, V200R007C02, V200R008C00, V200R008C10, V200R008C20, V200R008C30, AR510 V200R006C10, V200R006C12, V200R006C13, V200R006C15, V200R006C16, V200R006C17, V200R007C00, V200R008C20, V200R008C30, DP300 V500R002C00, IPS Module V100R001C10SPC200, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, MAX PRESENCE V100R001C00, NGFW Module V100R001C10SPC200, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R002C00, V500R002C10, NIP6300 V500R001C00, V500R001C20, V500R001C30, V500R001C50, NIP6600 V500R001C00, V500R001C20, V500R001C30, V500R001C50, NIP6800 V500R001C50, NetEngine16EX V200R006C10, V200R007C00, V200R008C20, V200R008C30, RP200 V500R002C00SPC200, V600R006C00, RSE6500 V500R002C00, SMC2.0 V100R003C10, V100R005C00, V500R002C00, V500R002C00T, V600R006C00, V600R006C00T, SRG1300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG2300 V200R006C10, V200R007C00, V200R007C02, V200R008C20, V200R008C30, SRG3300 V200R006C10, V200R007C00, V200R008C20, V200R008C30, SVN5600 V200R003C00, V200R003C10, SVN5800 V200R003C00, V200R003C10, SVN5800-C V200R003C00, V200R003C10, Secospace USG6300 V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, Secospace USG6500 V100R001C10, V100R001C20, V100R001C30, V500R001C00, V500R001C20, V500R001C30, V500R001C50, TE30 V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C01, V100R001C10, V500R002C00, V600R006C00, TP3106 V100R002C00, TP3206 V100R002C00, USG9500 V500R001C00, V500R001C20, V500R001C30, V500R001C50, USG9520 V300R001C01, V300R001C20, USG9560 V300R001C01, V300R001C20, USG9580 V300R001C01, V300R001C20, ViewPoint 9030 V100R011C02, V100R011C03, have a memory leak vulnerability in H323 protocol. The vulnerability is due to insufficient verification of the packets. An unauthenticated, remote attacker could exploit this vulnerability by sending crafted packets. A successful exploit could cause a memory leak and eventual denial of service (DoS) condition on an affected device.

INFO

Published Date :

Feb. 15, 2018, 4:29 p.m.

Last Modified :

Nov. 21, 2024, 3:14 a.m.

Remotely Exploitable :

Yes !

Impact Score :

1.4

Exploitability Score :

3.9
Affected Products

The following products are affected by CVE-2017-15332 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Huawei nip6800_firmware
2 Huawei usg9500_firmware
3 Huawei rse6500_firmware
4 Huawei dp300_firmware
5 Huawei te60_firmware
6 Huawei tp3106_firmware
7 Huawei viewpoint_9030_firmware
8 Huawei ar1200_firmware
9 Huawei ar200_firmware
10 Huawei ar3200_firmware
11 Huawei ar120-s_firmware
12 Huawei ar1200-s_firmware
13 Huawei ar150_firmware
14 Huawei ar150-s_firmware
15 Huawei ar160_firmware
16 Huawei ar200-s_firmware
17 Huawei ar2200_firmware
18 Huawei ar2200-s_firmware
19 Huawei ar510_firmware
20 Huawei netengine16ex_firmware
21 Huawei smc2.0_firmware
22 Huawei srg1300_firmware
23 Huawei srg2300_firmware
24 Huawei srg3300_firmware
25 Huawei secospace_usg6300_firmware
26 Huawei max_presence_firmware
27 Huawei tp3206_firmware
28 Huawei rp200_firmware
29 Huawei te30_firmware
30 Huawei te40_firmware
31 Huawei te50_firmware
32 Huawei secospace_usg6500_firmware
33 Huawei usg9520_firmware
34 Huawei usg9580_firmware
35 Huawei usg9560_firmware
36 Huawei ips_module_firmware
37 Huawei ngfw_module_firmware
38 Huawei nip6300_firmware
39 Huawei nip6600_firmware
40 Huawei svn5600_firmware
41 Huawei svn5800_firmware
42 Huawei svn5800-c_firmware
43 Huawei te30
44 Huawei te40
45 Huawei te50
46 Huawei te60
47 Huawei smc2.0
48 Huawei ar1200
49 Huawei ar150
50 Huawei ar160
51 Huawei ar200
52 Huawei ar2200
53 Huawei ar3200
54 Huawei nip6300
55 Huawei secospace_usg6500
56 Huawei usg9500
57 Huawei secospace_usg6300
58 Huawei ngfw_module
59 Huawei nip6600
60 Huawei ips_module
61 Huawei rse6500
62 Huawei usg9520
63 Huawei usg9580
64 Huawei usg9560
65 Huawei dp300
66 Huawei tp3106
67 Huawei viewpoint_9030
68 Huawei ar120-s
69 Huawei ar1200-s
70 Huawei ar150-s
71 Huawei ar200-s
72 Huawei ar2200-s
73 Huawei ar510
74 Huawei netengine16ex
75 Huawei srg1300
76 Huawei srg2300
77 Huawei srg3300
78 Huawei max_presence
79 Huawei tp3206
80 Huawei rp200
81 Huawei nip6800
82 Huawei svn5600
83 Huawei svn5800
84 Huawei svn5800-c
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2017-15332.

URL Resource
http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20171129-01-h323-en Vendor Advisory
http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20171129-01-h323-en Vendor Advisory

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2017-15332 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2017-15332 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by af854a3a-2127-422b-91ae-364da2661108

    Nov. 21, 2024

    Action Type Old Value New Value
    Added Reference http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20171129-01-h323-en
  • CVE Modified by [email protected]

    May. 14, 2024

    Action Type Old Value New Value
  • CWE Remap by [email protected]

    Oct. 03, 2019

    Action Type Old Value New Value
    Changed CWE CWE-399 CWE-772
  • Initial Analysis by [email protected]

    Mar. 01, 2018

    Action Type Old Value New Value
    Added CVSS V2 (AV:N/AC:L/Au:N/C:N/I:N/A:P)
    Added CVSS V3 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
    Changed Reference Type http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20171129-01-h323-en No Types Assigned http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20171129-01-h323-en Vendor Advisory
    Added CWE CWE-399
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar120-s_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar120-s_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar120-s_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar120-s_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar120-s:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar1200_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar1200_firmware:v200r006c13:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar1200_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar1200_firmware:v200r007c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar1200_firmware:v200r007c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar1200_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar1200_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar1200:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar1200-s_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar1200-s_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar1200-s_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar1200-s_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar1200-s:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar150_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar150_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar150_firmware:v200r007c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar150_firmware:v200r007c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar150_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar150_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar150:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar150-s_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar150-s_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar150-s_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar150-s_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar150-s:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar160_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar160_firmware:v200r006c12:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar160_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar160_firmware:v200r007c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar160_firmware:v200r007c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar160_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar160_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar160:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar200_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar200_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar200_firmware:v200r007c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar200_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar200_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar200:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar200-s_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar200-s_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar200-s_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar200-s_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar200-s:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar2200_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar2200_firmware:v200r006c13:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar2200_firmware:v200r006c16pwe:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar2200_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar2200_firmware:v200r007c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar2200_firmware:v200r007c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar2200_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar2200_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar2200:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar2200-s_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar2200-s_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar2200-s_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar2200-s_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar2200-s:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar3200_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar3200_firmware:v200r006c11:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar3200_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar3200_firmware:v200r007c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar3200_firmware:v200r007c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar3200_firmware:v200r008c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar3200_firmware:v200r008c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar3200_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar3200_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar3200:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ar510_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar510_firmware:v200r006c12:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar510_firmware:v200r006c13:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar510_firmware:v200r006c15:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar510_firmware:v200r006c16:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar510_firmware:v200r006c17:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar510_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar510_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ar510_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ar510:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:netengine16ex_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:netengine16ex_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:netengine16ex_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:netengine16ex_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:netengine16ex:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:srg1300_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:srg1300_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:srg1300_firmware:v200r007c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:srg1300_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:srg1300_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:srg1300:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:srg2300_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:srg2300_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:srg2300_firmware:v200r007c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:srg2300_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:srg2300_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:srg2300:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:srg3300_firmware:v200r006c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:srg3300_firmware:v200r007c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:srg3300_firmware:v200r008c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:srg3300_firmware:v200r008c30:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:srg3300:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:dp300_firmware:v500r002c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:dp300:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ips_module_firmware:v100r001c10spc200:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ips_module_firmware:v100r001c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ips_module_firmware:v100r001c30:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ips_module_firmware:v500r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ips_module_firmware:v500r001c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ips_module_firmware:v500r001c30:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ips_module_firmware:v500r001c50:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ips_module:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:max_presence_firmware:v100r001c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:max_presence:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:ngfw_module_firmware:v100r001c10spc200:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ngfw_module_firmware:v100r001c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ngfw_module_firmware:v100r001c30:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ngfw_module_firmware:v500r001c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ngfw_module_firmware:v500r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:ngfw_module_firmware:v500r002c10:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:ngfw_module:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:nip6300_firmware:v500r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:nip6300_firmware:v500r001c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:nip6300_firmware:v500r001c30:*:*:*:*:*:*:* *cpe:2.3:o:huawei:nip6300_firmware:v500r001c50:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:nip6300:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:nip6600_firmware:v500r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:nip6600_firmware:v500r001c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:nip6600_firmware:v500r001c30:*:*:*:*:*:*:* *cpe:2.3:o:huawei:nip6600_firmware:v500r001c50:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:nip6600:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:nip6800_firmware:v500r001c50:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:nip6800:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:rp200_firmware:v500r002c00spc200:*:*:*:*:*:*:* *cpe:2.3:o:huawei:rp200_firmware:v600r006c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:rp200:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:rse6500_firmware:v500r002c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:rse6500:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:smc2.0_firmware:v100r003c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:smc2.0_firmware:v100r005c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:smc2.0_firmware:v500r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:smc2.0_firmware:v500r002c00t:*:*:*:*:*:*:* *cpe:2.3:o:huawei:smc2.0_firmware:v600r006c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:smc2.0_firmware:v600r006c00t:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:smc2.0:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:svn5600_firmware:v200r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:svn5600_firmware:v200r003c10:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:svn5600:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:svn5800_firmware:v200r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:svn5800_firmware:v200r003c10:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:svn5800:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:svn5800-c_firmware:v200r003c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:svn5800-c_firmware:v200r003c10:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:svn5800-c:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:secospace_usg6300_firmware:v100r001c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6300_firmware:v100r001c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6300_firmware:v100r001c30:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c30:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6300_firmware:v500r001c50:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:secospace_usg6300:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:secospace_usg6500_firmware:v100r001c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6500_firmware:v100r001c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6500_firmware:v100r001c30:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c30:*:*:*:*:*:*:* *cpe:2.3:o:huawei:secospace_usg6500_firmware:v500r001c50:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:secospace_usg6500:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:te30_firmware:v100r001c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:te30_firmware:v500r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:te30_firmware:v600r006c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:te30:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:te40_firmware:v500r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:te40_firmware:v600r006c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:te40:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:te50_firmware:v500r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:te50_firmware:v600r006c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:te50:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:te60_firmware:v100r001c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:te60_firmware:v100r001c10:*:*:*:*:*:*:* *cpe:2.3:o:huawei:te60_firmware:v500r002c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:te60_firmware:v600r006c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:te60:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:tp3106_firmware:v100r002c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:tp3106:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:tp3206_firmware:v100r002c00:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:tp3206:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:usg9500_firmware:v500r001c00:*:*:*:*:*:*:* *cpe:2.3:o:huawei:usg9500_firmware:v500r001c20:*:*:*:*:*:*:* *cpe:2.3:o:huawei:usg9500_firmware:v500r001c30:*:*:*:*:*:*:* *cpe:2.3:o:huawei:usg9500_firmware:v500r001c50:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:usg9500:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:usg9520_firmware:v300r001c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:usg9520_firmware:v300r001c20:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:usg9520:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:usg9560_firmware:v300r001c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:usg9560_firmware:v300r001c20:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:usg9560:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:usg9580_firmware:v300r001c01:*:*:*:*:*:*:* *cpe:2.3:o:huawei:usg9580_firmware:v300r001c20:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:usg9580:-:*:*:*:*:*:*:*
    Added CPE Configuration AND OR *cpe:2.3:o:huawei:viewpoint_9030_firmware:v100r011c02:*:*:*:*:*:*:* *cpe:2.3:o:huawei:viewpoint_9030_firmware:v100r011c03:*:*:*:*:*:*:* OR cpe:2.3:h:huawei:viewpoint_9030:-:*:*:*:*:*:*:*
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2017-15332 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2017-15332 weaknesses.

Exploit Prediction

EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.

0.19 }} 0.02%

score

0.57607

percentile

CVSS30 - Vulnerability Scoring System
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability