Google Android 11.0/12.0/13.0 a2dp_sbc.cc A2DP_BuildCodecHeaderSbc out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Google Android 11.0/12.0/13.0. Affected by this vulnerability is the function A2DP_BuildCodecHeaderSbc of the file a2dp_sbc.cc. The manipulation leads to out-of-bounds write.
This vulnerability is listed as CVE-2023-20952. The attack must be carried out locally. There is no available exploit.
To fix this issue, it is recommended to deploy a patch.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability was found in Google Android 11.0/12.0/13.0 (Smartphone Operating System). It has been rated as problematic. This issue affects the function A2DP_BuildCodecHeaderSbc of the file a2dp_sbc.cc. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality. The summary by CVE is:
In A2DP_BuildCodecHeaderSbc of a2dp_sbc.cc, there is a possible out of bounds write due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12L Android-13Android ID: A-186803518
The weakness was presented 03/25/2023 as A-186803518. It is possible to read the advisory at source.android.com. The identification of this vulnerability is CVE-2023-20952 since 11/03/2022. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/06/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 vulnerability database at EUVD (EUVD-2023-25120). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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.4VulDB Meta Temp Score: 4.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.5
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: Out-of-bounds writeCWE: CWE-787 / CWE-119
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
11/03/2022 🔍03/25/2023 🔍
03/25/2023 🔍
09/06/2025 🔍
Sources
Vendor: google.comAdvisory: A-186803518
Status: Confirmed
CVE: CVE-2023-20952 (🔍)
GCVE (CVE): GCVE-0-2023-20952
GCVE (VulDB): GCVE-100-223883
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 03/25/2023 08:07 AMUpdated: 09/06/2025 09:13 PM
Changes: 03/25/2023 08:07 AM (43), 04/14/2023 02:10 PM (11), 09/06/2025 09:13 PM (16)
Complete: 🔍
Cache ID: 244:ABD:40
No comments yet. Languages: en.
Please log in to comment.