Google Android crus_sp_shared_ioctl size memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.2 | $5k-$25k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Google Android. Affected by this vulnerability is the function crus_sp_shared_ioctl. Performing a manipulation of the argument size as part of Parameter results in memory corruption.
This vulnerability was named CVE-2020-0235. The attack may be initiated remotely. There is no available exploit.
It is recommended to apply a patch to fix this issue.
Details
A vulnerability, which was classified as critical, was found in Google Android (Smartphone Operating System) (the affected version is unknown). This affects the function crus_sp_shared_ioctl. The manipulation of the argument size as part of a Parameter leads to a memory corruption vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In crus_sp_shared_ioctl we first copy 4 bytes from userdata into "size" variable, and then use that variable as the size parameter for "copy_from_user", ending up overwriting memory following "crus_sp_hdr". "crus_sp_hdr" is a static variable, of type "struct crus_sp_ioctl_header".Product: AndroidVersions: Android kernelAndroid ID: A-135129430
The weakness was presented 06/16/2020. This vulnerability is uniquely identified as CVE-2020-0235 since 10/17/2019. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 06/17/2020). 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.
See VDB-156782, VDB-156781 and VDB-156780 for similar entries. Be aware that VulDB is the high quality 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: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
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
Class: Memory corruptionCWE: 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
10/17/2019 🔍06/16/2020 🔍
06/17/2020 🔍
06/17/2020 🔍
Sources
Vendor: google.comStatus: Not defined
CVE: CVE-2020-0235 (🔍)
GCVE (CVE): GCVE-0-2020-0235
GCVE (VulDB): GCVE-100-156783
scip Labs: https://www.scip.ch/en/?labs.20150917
See also: 🔍
Entry
Created: 06/17/2020 06:41Updated: 06/17/2020 10:06
Changes: 06/17/2020 06:41 (39), 06/17/2020 10:06 (18)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.