Google Android sha256_core.c sec_SHA256_Transform information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.2 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Google Android. Impacted is the function sec_SHA256_Transform of the file sha256_core.c. Executing a manipulation can lead to information disclosure.
This vulnerability is tracked as CVE-2021-39680. The attack is restricted to local execution. No exploit exists.
It is advisable to implement a patch to correct this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (affected version unknown). It has been declared as problematic. This vulnerability affects the function sec_SHA256_Transform of the file sha256_core.c. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality.
The weakness was disclosed 01/15/2022 as A-197965864. The advisory is shared for download at source.android.com. This vulnerability was named CVE-2021-39680 since 08/23/2021. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
Applying a patch is able to eliminate this problem.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.3VulDB Meta Temp Score: 2.2
VulDB Base Score: 2.3
VulDB Temp Score: 2.2
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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 🔍01/15/2022 🔍
01/15/2022 🔍
01/19/2022 🔍
Sources
Vendor: google.comAdvisory: A-197965864
Status: Confirmed
CVE: CVE-2021-39680 (🔍)
GCVE (CVE): GCVE-0-2021-39680
GCVE (VulDB): GCVE-100-190492
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 01/15/2022 07:18Updated: 01/19/2022 08:37
Changes: 01/15/2022 07:18 (41), 01/19/2022 08:37 (1)
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.