Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY6 SECURITY RECORDS

Huawei Technologies Co., Ltd.

Nice-AL00

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2017-8184 22 Nov 2017 Earlier than Nice-AL00C00B160 versions, Earlier than Nice-AL10C00B140 versions No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-8183 22 Nov 2017 Earlier than Nice-AL00C00B160 versions, Earlier than Nice-AL10C00B140 versions No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-8182 22 Nov 2017 Earlier than Nice-AL00C00B160 versions, Earlier than Nice-AL10C00B140 versions No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-8181 22 Nov 2017 Versions earlier than Nice-AL00C00B155 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-8180 22 Nov 2017 Versions earlier than Nice-AL00C00B155 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-8179 22 Nov 2017 Versions earlier than Nice-AL00C00B155 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.