Google Android RCS Service ShannonRcsService.java registerGsmaServiceIntentReceiver permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android. It has been classified as critical. Affected by this vulnerability is the function registerGsmaServiceIntentReceiver of the file ShannonRcsService.java of the component RCS Service. This manipulation causes permission.
This vulnerability appears as CVE-2023-21149. The attack requires local access. There is no available exploit.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability has been found in Google Android (Smartphone Operating System) (unknown version) and classified as critical. Affected by this vulnerability is the function registerGsmaServiceIntentReceiver of the file ShannonRcsService.java of the component RCS Service. The manipulation with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In registerGsmaServiceIntentReceiver of ShannonRcsService.java, there is a possible way to activate/deactivate RCS service due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-270050709References: N/A
The weakness was presented 06/28/2023 as A-270050709. The advisory is shared at source.android.com. This vulnerability is known as CVE-2023-21149 since 11/03/2022. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/13/2025). It is expected to see the exploit prices for this product increasing in the near future.MITRE ATT&CK project uses the attack technique T1222 for this issue.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-25317). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: PermissionCWE: CWE-275 / CWE-266
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 🔍06/28/2023 🔍
06/28/2023 🔍
09/13/2025 🔍
Sources
Vendor: google.comAdvisory: A-270050709
Status: Confirmed
CVE: CVE-2023-21149 (🔍)
GCVE (CVE): GCVE-0-2023-21149
GCVE (VulDB): GCVE-100-232573
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 06/28/2023 21:47Updated: 09/13/2025 18:19
Changes: 06/28/2023 21:47 (43), 07/20/2023 16:05 (11), 09/13/2025 18:19 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.