Huawei CloudEngine Label Distribution Protocol LDP Packet resource management

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Huawei CloudEngine. It has been rated as problematic. This issue affects some unknown processing of the component Label Distribution Protocol. Performing a manipulation as part of LDP Packet results in resource management. This vulnerability is identified as CVE-2016-8784. The attack can only be performed from the local network. There is not any exploit available. Upgrading the affected component is advised.
Details
A vulnerability was found in Huawei CloudEngine (Cloud Software) (version unknown). It has been classified as problematic. This affects an unknown function of the component Label Distribution Protocol. The manipulation as part of a LDP Packet leads to a resource management vulnerability. CWE is classifying the issue as CWE-399. This is going to have an impact on availability. The summary by CVE is:
Huawei CloudEngine 12800 V100R003C00, V100R003C10, V100R005C00, V100R005C10, V100R006C00 have a memory leak vulnerability. An unauthenticated attacker may send specific Label Distribution Protocol (LDP) packets to the devices. When the values of some parameters in the packet are abnormal, the LDP processing module does not release the memory to handle the packet, resulting in memory leak.
The bug was discovered 12/21/2016. The weakness was released 03/09/2018 (Website). The advisory is shared at huawei.com. This vulnerability is uniquely identified as CVE-2016-8784 since 10/18/2016. The exploitability is told to be easy. The attack needs to approached within the local network. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 443 days. During that time the estimated underground price was around $5k-$25k.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 95079†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.huawei.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Resource managementCWE: CWE-399 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
10/18/2016 🔍12/21/2016 🔍
12/23/2016 🔍
03/09/2018 🔍
03/09/2018 🔍
03/10/2018 🔍
02/17/2023 🔍
Sources
Vendor: huawei.comAdvisory: sa-20161221-01
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-8784 (🔍)
GCVE (CVE): GCVE-0-2016-8784
GCVE (VulDB): GCVE-100-114261
SecurityFocus: 95079 - Multiple Huawei Products CVE-2016-8784 Denial of Service Vulnerability
Entry
Created: 03/10/2018 15:25Updated: 02/17/2023 19:02
Changes: 03/10/2018 15:25 (60), 01/11/2020 16:53 (4), 02/17/2023 19:02 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.