| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Huawei HiSilicon. The impacted element is the function printf. This manipulation causes memory corruption.
This vulnerability is handled as CVE-2020-24214. The attack can be initiated remotely. Additionally, an exploit exists.
There are still doubts about whether this vulnerability truly exists.
Details
A vulnerability classified as critical was found in Huawei HiSilicon (the affected version is unknown). Affected by this vulnerability is the function printf. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was released 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 known as CVE-2020-24214. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known.
A public exploit has been developed by Alexei Kojenov and been published immediately after the advisory. It is possible to download the exploit at kojenov.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $5k-$25k. 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 (48903). Entries connected to this vulnerability are available at VDB-161637, VDB-161638, VDB-161639 and VDB-161640. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: 7.3VulDB Meta Temp Score: 6.6
VulDB Base Score: 7.3
VulDB Temp Score: 6.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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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/14/2024 🔍
Sources
Vendor: huawei.comAdvisory: kojenov.com
Researcher: Alexei Kojenov
Status: Not defined
Confirmation: 🔍
Disputed: 🔍
CVE: CVE-2020-24214 (🔍)
GCVE (CVE): GCVE-0-2020-24214
GCVE (VulDB): GCVE-100-161641
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 09/19/2020 17:17Updated: 07/14/2024 04:23
Changes: 09/19/2020 17:17 (52), 09/19/2020 17:22 (1), 07/14/2024 04:23 (15)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

No comments yet. Languages: en.
Please log in to comment.