← Search results
CVE-LINKED INVENTORY28 SECURITY RECORDS
Huawei Technologies Co., Ltd.
DP300, RP200, TE30, TE40, TE50, TE60
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2017-17316 | 2 Jul 2018 | DP300 V500R002C00; RP200 V500R002C00; V600R006C00; TE30 V100R001C10; V500R002C00; TE40 V500R002C00; TE50 V500R002C00; TE60 V100R001C10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17315 | 24 May 2018 | DP300 V500R002C00; RP200 V600R006C00; TE30 V100R001C10; V500R002C00; V600R006C00; TE40 V500R002C00; TE50 V500R002C00; TE60 V100R001C10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17314 | 30 Apr 2018 | DP300 V500R002C00, RP200 V600R006C00, TE30 V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C10, V500R002C00, V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17310 | 19 Apr 2018 | DP300 V500R002C00, RP200 V600R006C00, TE30 V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C10, V500R002C00, V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17308 | 11 Apr 2018 | DP300 V500R002C00, RP200 V500R002C00, V600R006C00, TE30 V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C10, V500R002C00, V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17282 | 9 Mar 2018 | DP300 V500R002C00, RP200 V500R002C00, V600R006C00, TE30 V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C10, V500R002C00, V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-15314 | 9 Mar 2018 | DP300 V500R002C00, RP200 V500R002C00SPC200, V600R006C00, TE30 V100R001C10SPC300, V100R001C10SPC500, V100R001C10SPC600, V100R001C10SPC700, V500R002C00SPC200, V500R002C00SPC500, V500R002C00SPC600, V500R002C00SPC700, V500R002C00SPC900, V500R002C00SPCb00, V600R006C00, TE40 V500R002C00SPC600, V500R002C00SPC700, V500R002C00SPC900, V500R002C00SPCb00, V600R006C00, TE50 V500R002C00SPC600, V500R002C00SPC700, V500R002C00SPCb00, V600R006C00, TE60 V100R001C10, V500R002C00, V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17303 | 9 Mar 2018 | DP300 V500R002C00; V500R002C00B010; V500R002C00B011; V500R002C00B012; V500R002C00B013; V500R002C00B014; V500R002C00B017; V500R002C00B018 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17281 | 9 Mar 2018 | DP300 V500R002C00; RP200 V600R006C00; TE30 V100R001C10; V500R002C00; V600R006C00; TE40 V500R002C00; TE50 V500R002C00; TE60 V100R001C10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17220 | 9 Mar 2018 | DP300 V500R002C00; RP200 V500R002C00; V600R006C00; TE30 V100R001C10; V500R002C00; TE40 V500R002C00; TE50 V500R002C00; TE60 V100R001C10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17219 | 9 Mar 2018 | DP300 V500R002C00; RP200 V500R002C00; V600R006C00; TE30 V100R001C10; V500R002C00; TE40 V500R002C00; TE50 V500R002C00; TE60 V100R001C10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17217 | 9 Mar 2018 | DP300 V500R002C00; RP200 V500R002C00SPC200; V600R006C00; TE30 V100R001C10; V500R002C00; TE40 V500R002C00; TE50 V500R002C00; TE60 V100R001C10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17216 | 9 Mar 2018 | DP300 V500R002C00; RP200 V500R002C00SPC200; V600R006C00; TE30 V100R001C10; V500R002C00; TE40 V500R002C00; TE50 V500R002C00; TE60 V100R001C10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17200 | 9 Mar 2018 | DP300 V500R002C00; RP200 V500R002C00; V600R006C00; TE30 V100R001C10; V500R002C00; TE40 V500R002C00; TE50 V500R002C00; TE60 V100R001C10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17199 | 9 Mar 2018 | DP300 V500R002C00; RP200 V500R002C00; V600R006C00; TE30 V100R001C10; V500R002C00; TE40 V500R002C00; TE50 V500R002C00; TE60 V100R001C10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17150 | 9 Mar 2018 | DP300 V500R002C00; RP200 V500R002C00; V600R006C00; TE30 V100R001C10; V500R002C00; TE40 V500R002C00; TE50 V500R002C00; TE60 V100R001C10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17134 | 5 Mar 2018 | DP300 V500R002C00; RP200 V500R002C00SPC200; V600R006C00; TE30 V100R001C10; V500R002C00; TE40 V500R002C00; TE50 V500R002C00; TE60 V100R001C10 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17302 | 15 Feb 2018 | DP300 V500R002C00, RP200 V600R006C00, TE30 V100R001C10, V500R002C00, V600R006C00, TE40 V500R002C00, V600R006C00, TE50 V500R002C00, V600R006C00, TE60 V100R001C10, V500R002C00, V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17289 | 15 Feb 2018 | DP300 V500R002C00,RP200 V500R002C00, V600R006C00,TE30 V100R001C10, V500R002C00, V600R006C00,TE40 V500R002C00, V600R006C00,TE50 V500R002C00, V600R006C00,TE60 V100R001C10, V500R002C00, V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17288 | 15 Feb 2018 | DP300 V500R002C00,RP200 V500R002C00, V600R006C00,TE30 V100R001C10, V500R002C00, V600R006C00,TE40 V500R002C00, V600R006C00,TE50 V500R002C00, V600R006C00,TE60 V100R001C10, V500R002C00, V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17284 | 15 Feb 2018 | DP300 V500R002C00,RP200 V500R002C00, V600R006C00,TE30 V100R001C10, V500R002C00, V600R006C00,TE40 V500R002C00, V600R006C00,TE50 V500R002C00, V600R006C00,TE60 V100R001C01, V100R001C10, V500R002C00, V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17283 | 15 Feb 2018 | DP300 V500R002C00,RP200 V500R002C00, V600R006C00,TE30 V100R001C10, V500R002C00, V600R006C00,TE40 V500R002C00, V600R006C00,TE50 V500R002C00, V600R006C00,TE60 V100R001C01, V100R001C10, V500R002C00, V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17187 | 15 Feb 2018 | DP300 V500R002C00, RP200 V500R002C00,V600R006C00, TE30 V100R001C10,V500R002C00,V600R006C00, TE40 V500R002C00,V600R006C00, TE50 V500R002C00,V600R006C00, TE60 V100R001C10,V500R002C00,V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17186 | 15 Feb 2018 | DP300 V500R002C00, RP200 V500R002C00,V600R006C00, TE30 V100R001C10,V500R002C00,V600R006C00, TE40 V500R002C00,V600R006C00, TE50 V500R002C00,V600R006C00, TE60 V100R001C10,V500R002C00,V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17185 | 15 Feb 2018 | DP300 V500R002C00, RP200 V500R002C00,V600R006C00, TE30 V100R001C10,V500R002C00,V600R006C00, TE40 V500R002C00,V600R006C00, TE50 V500R002C00,V600R006C00, TE60 V100R001C10,V500R002C00,V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17184 | 15 Feb 2018 | DP300 V500R002C00, RP200 V500R002C00,V600R006C00, TE30 V100R001C10,V500R002C00,V600R006C00, TE40 V500R002C00,V600R006C00, TE50 V500R002C00,V600R006C00, TE60 V100R001C10,V500R002C00,V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17183 | 15 Feb 2018 | DP300 V500R002C00, RP200 V500R002C00,V600R006C00, TE30 V100R001C10,V500R002C00,V600R006C00, TE40 V500R002C00,V600R006C00, TE50 V500R002C00,V600R006C00, TE60 V100R001C10,V500R002C00,V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2017-17182 | 15 Feb 2018 | DP300 V500R002C00, RP200 V500R002C00,V600R006C00, TE30 V100R001C10,V500R002C00,V600R006C00, TE40 V500R002C00,V600R006C00, TE50 V500R002C00,V600R006C00, TE60 V100R001C10,V500R002C00,V600R006C00 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.