| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Huawei HiSilicon. It has been rated as critical. This vulnerability affects unknown code. Performing a manipulation results in backdoor. This vulnerability is reported as CVE-2020-24215. Moreover, an exploit is present. It is still unclear if this vulnerability genuinely exists.
Details
A vulnerability was found in Huawei HiSilicon (version unknown). It has been classified as critical. This affects an unknown function. The manipulation with an unknown input leads to a backdoor vulnerability. CWE is classifying the issue as CWE-912. The product contains functionality that is not documented, not part of the specification, and not accessible through an interface or command sequence that is obvious to the product's users or administrators. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was disclosed 09/15/2020 by Alexei Kojenov as not defined advisory (Website). The advisory is shared at kojenov.com. The public release happened without involvement of Huawei. The advisory contains:
This article discloses critical vulnerabilities in IPTV/H.264/H.265 video encoders based on HiSilicon hi3520d hardware.This vulnerability is uniquely identified as CVE-2020-24215. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1588.001 for this issue.
A public exploit has been developed by Alexei Kojenov and been published immediately after the advisory. The exploit is shared for download at kojenov.com. It is declared as proof-of-concept. The real existence of this vulnerability is still doubted at the moment.
The advisory contains the following remark:
Huawei issued a statement saying that none of the vulnerabilities have been introduced by HiSilicon chips and SDK packages.
The vulnerability is also documented in the vulnerability database at Exploit-DB (48902). The entries VDB-161638, VDB-161639, VDB-161640 and VDB-161641 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
License
Website
- Vendor: https://www.huawei.com/
CPE 2.3
CPE 2.2
Video

CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.4VulDB Meta Temp Score: 7.6
VulDB Base Score: 8.4
VulDB Temp Score: 7.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: BackdoorCWE: CWE-912
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: Alexei Kojenov
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Exploit Delay Time: 🔍
Timeline
09/15/2020 🔍09/15/2020 🔍
09/17/2020 🔍
09/19/2020 🔍
07/10/2024 🔍
Sources
Vendor: huawei.comAdvisory: kojenov.com
Researcher: Alexei Kojenov
Status: Not defined
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2020-24215 (🔍)
GCVE (CVE): GCVE-0-2020-24215
GCVE (VulDB): GCVE-100-161637
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 09/19/2020 17:16Updated: 07/10/2024 16:16
Changes: 09/19/2020 17:16 (51), 09/19/2020 17:21 (1), 07/10/2024 16:16 (16)
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.