Google Android aoc.c aoc_unlocked_ioctl type confusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.7 | $5k-$25k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Google Android. Affected is the function aoc_unlocked_ioctl of the file aoc.c. The manipulation leads to type confusion.
This vulnerability is traded as CVE-2024-27236. An attack has to be approached locally. There is no exploit available.
It is suggested to install a patch to address this issue.
Details
A vulnerability was found in Google Android (Smartphone Operating System) (version now known). It has been rated as problematic. This issue affects the function aoc_unlocked_ioctl of the file aoc.c. The manipulation with an unknown input leads to a type confusion vulnerability. Using CWE to declare the problem leads to CWE-843. The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In aoc_unlocked_ioctl of aoc.c, there is a possible memory corruption due to type confusion. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
The weakness was shared 03/11/2024. The advisory is shared at source.android.com. The identification of this vulnerability is CVE-2024-27236 since 02/21/2024. 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 08/27/2024). 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
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.4
CNA 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: 🔍
Exploiting
Class: Type confusionCWE: CWE-843
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
02/21/2024 🔍03/11/2024 🔍
03/11/2024 🔍
08/27/2024 🔍
Sources
Vendor: google.comAdvisory: source.android.com
Status: Confirmed
CVE: CVE-2024-27236 (🔍)
GCVE (CVE): GCVE-0-2024-27236
GCVE (VulDB): GCVE-100-256409
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 03/11/2024 20:51Updated: 08/27/2024 21:23
Changes: 03/11/2024 20:51 (40), 08/27/2024 21:23 (27)
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.