Huawei XH620 V3/XH622 V3/XH628 V3 Login Brute Force improper authorization

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.6 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Huawei XH620 V3, XH622 V3 and XH628 V3. The affected element is an unknown function of the component Login. Executing a manipulation can lead to improper authorization (Brute Force). This vulnerability is tracked as CVE-2016-6825. The attack can be launched remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability has been found in Huawei XH620 V3, XH622 V3 and XH628 V3 (affected version unknown) and classified as critical. This vulnerability affects an unknown functionality of the component Login. The manipulation with an unknown input leads to a improper authorization vulnerability (Brute Force). The CWE definition for the vulnerability is CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Huawei XH620 V3, XH622 V3, and XH628 V3 servers with software before V100R003C00SPC610, RH1288 V3 servers with software before V100R003C00SPC613, RH2288 V3 servers with software before V100R003C00SPC617, and RH2288H V3 servers with software before V100R003C00SPC515 allow remote attackers to obtain passwords via a brute-force attack, related to "lack of authentication protection mechanisms."
The weakness was disclosed 09/07/2016 (Website). The advisory is shared for download at huawei.com. This vulnerability was named CVE-2016-6825 since 08/16/2016. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1548.002.
Upgrading eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 92504†). Once again VulDB remains the best source for vulnerability data.
Product
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: 9.8VulDB Meta Temp Score: 9.6
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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
Name: Brute ForceClass: Improper authorization / Brute Force
CWE: CWE-285 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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
08/16/2016 🔍08/17/2016 🔍
09/07/2016 🔍
09/07/2016 🔍
09/08/2016 🔍
09/15/2022 🔍
Sources
Vendor: huawei.comAdvisory: sa-20160817-01
Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-6825 (🔍)
GCVE (CVE): GCVE-0-2016-6825
GCVE (VulDB): GCVE-100-91372
SecurityFocus: 92504 - Multiple Huawei Servers CVE-2016-6825 Brute Force Authentication Bypass Vulnerability
Entry
Created: 09/08/2016 21:59Updated: 09/15/2022 09:34
Changes: 09/08/2016 21:59 (50), 04/12/2019 06:55 (12), 09/15/2022 09:34 (4)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.