Google Android 12.0/13.0 attribution_processor.cc OnWakelockReleased use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Google Android 12.0/13.0. Impacted is the function OnWakelockReleased of the file attribution_processor.cc. Executing a manipulation can lead to use after free.
This vulnerability appears as CVE-2023-21096. The attack may be performed from remote. There is no available exploit.
A patch should be applied to remediate this issue.
Details
A vulnerability has been found in Google Android 12.0/13.0 (Smartphone Operating System) and classified as critical. This vulnerability affects the function OnWakelockReleased of the file attribution_processor.cc. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
In OnWakelockReleased of attribution_processor.cc, there is a use after free that could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-12 Android-12L Android-13Android ID: A-254774758
The weakness was presented 04/20/2023 as A-254774758. The advisory is available at source.android.com. This vulnerability was named CVE-2023-21096 since 11/03/2022. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 09/10/2025). 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.
The vulnerability is also documented in the databases at EUVD (EUVD-2023-25264) and CERT Bund (WID-SEC-2023-0841). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Affected
- Samsung Exynos
- Samsung Android
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: 8.0VulDB Meta Temp Score: 7.9
VulDB Base Score: 6.3
VulDB Temp Score: 6.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: 🔍
Exploiting
Class: Use after freeCWE: CWE-416 / 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
11/03/2022 🔍04/20/2023 🔍
04/20/2023 🔍
09/10/2025 🔍
Sources
Vendor: google.comAdvisory: A-254774758
Status: Confirmed
CVE: CVE-2023-21096 (🔍)
GCVE (CVE): GCVE-0-2023-21096
GCVE (VulDB): GCVE-100-226858
EUVD: 🔍
CERT Bund: WID-SEC-2023-0841 - Samsung Android und Samsung Exynos: Mehrere Schwachstellen
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 04/20/2023 07:29Updated: 09/10/2025 23:54
Changes: 04/20/2023 07:29 (42), 05/14/2023 09:33 (11), 09/04/2025 02:27 (22), 09/10/2025 23:54 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.