Huawei iManager NetEco Firmware Update integrity check

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.9$5k-$25k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Huawei iManager NetEco. The affected element is an unknown function of the component Firmware Update Handler. Performing a manipulation results in integrity check. This vulnerability is known as CVE-2021-37127. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Huawei iManager NetEco (affected version not known). This affects some unknown functionality of the component Firmware Update Handler. The manipulation with an unknown input leads to a integrity check vulnerability. CWE is classifying the issue as CWE-354. The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission. This is going to have an impact on integrity, and availability.

The weakness was published 10/27/2021 as huawei-sa-20211020-01. The advisory is shared at huawei.com. This vulnerability is uniquely identified as CVE-2021-37127 since 07/20/2021. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 10/31/2021).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.9
VulDB Meta Temp Score: 5.9

VulDB Base Score: 4.6
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.2
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Integrity check
CWE: CWE-354 / CWE-345
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

07/20/2021 🔍
10/27/2021 +99 days 🔍
10/27/2021 +0 days 🔍
10/31/2021 +4 days 🔍

Sourcesinfo

Vendor: huawei.com

Advisory: huawei-sa-20211020-01
Status: Confirmed

CVE: CVE-2021-37127 (🔍)
GCVE (CVE): GCVE-0-2021-37127
GCVE (VulDB): GCVE-100-185565

Entryinfo

Created: 10/27/2021 10:40
Updated: 10/31/2021 18:56
Changes: 10/27/2021 10:40 (37), 10/31/2021 18:48 (1), 10/31/2021 18:56 (18)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!