Google Android 10.0/11.0/12.0 ih264d_parse_slice.c ih264d_parse_decode_slice out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Google Android 10.0/11.0/12.0. Affected by this issue is the function ih264d_parse_decode_slice of the file ih264d_parse_slice.c. Performing a manipulation results in out-of-bounds write.
This vulnerability was named CVE-2021-39667. The attack may be initiated remotely. There is no available exploit.
It is suggested to install a patch to address this issue.
Details
A vulnerability classified as critical has been found in Google Android 10.0/11.0/12.0 (Smartphone Operating System). This affects the function ih264d_parse_decode_slice of the file ih264d_parse_slice.c. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality.
The weakness was presented 03/16/2022 as A-205702093. The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2021-39667 since 08/23/2021. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/16/2022). It is expected to see the exploit prices for this product increasing in the near future.
Applying a patch is able to eliminate this problem.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
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: Out-of-bounds writeCWE: CWE-787 / CWE-119
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: PatchStatus: 🔍
0-Day Time: 🔍
Timeline
08/23/2021 🔍03/16/2022 🔍
03/16/2022 🔍
03/19/2022 🔍
Sources
Vendor: google.comAdvisory: A-205702093
Status: Confirmed
CVE: CVE-2021-39667 (🔍)
GCVE (CVE): GCVE-0-2021-39667
GCVE (VulDB): GCVE-100-195273
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 03/16/2022 22:32Updated: 03/19/2022 12:02
Changes: 03/16/2022 22:32 (42), 03/19/2022 12:02 (1)
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.