Google Android 11.0/12.0/13.0 sdp_db.cc SDP_AddAttribute out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.9 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Google Android 11.0/12.0/13.0. Impacted is the function SDP_AddAttribute of the file sdp_db.cc. Performing a manipulation results in out-of-bounds write.
This vulnerability was named CVE-2023-20954. The attack may be initiated remotely. There is no available exploit.
It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as critical, was found in Google Android 11.0/12.0/13.0 (Smartphone Operating System). This affects the function SDP_AddAttribute of the file sdp_db.cc. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
In SDP_AddAttribute of sdp_db.cc, there is a possible out of bounds write due to an incorrect bounds check. This could lead to remote code execution 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-261867748
The weakness was presented 03/25/2023 as A-261867748. The advisory is shared at source.android.com. This vulnerability is uniquely identified as CVE-2023-20954 since 11/03/2022. 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 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-25122). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
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: Out-of-bounds writeCWE: CWE-787 / 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 🔍03/25/2023 🔍
03/25/2023 🔍
09/06/2025 🔍
Sources
Vendor: google.comAdvisory: A-261867748
Status: Confirmed
CVE: CVE-2023-20954 (🔍)
GCVE (CVE): GCVE-0-2023-20954
GCVE (VulDB): GCVE-100-223833
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 03/25/2023 07:46Updated: 09/06/2025 21:13
Changes: 03/25/2023 07:46 (43), 04/14/2023 10:56 (11), 09/06/2025 21:13 (16)
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.