Google Android 13.0 PasspointXmlUtils.java serializePasspointConfiguration information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Google Android 13.0. The affected element is the function serializePasspointConfiguration of the file PasspointXmlUtils.java. Executing a manipulation can lead to information disclosure.
The identification of this vulnerability is CVE-2023-21027. The attack may be launched remotely. There is no exploit available.
A patch should be applied to remediate this issue.
Details
A vulnerability has been found in Google Android 13.0 (Smartphone Operating System) and classified as problematic. This vulnerability affects the function serializePasspointConfiguration of the file PasspointXmlUtils.java. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:
In serializePasspointConfiguration of PasspointXmlUtils.java, there is a possible logic error in the code. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-216854451
The weakness was shared 03/25/2023 as A-216854451. The advisory is available at source.android.com. This vulnerability was named CVE-2023-21027 since 11/03/2022. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 09/08/2025). It is expected to see the exploit prices for this product increasing in the near future.This vulnerability is assigned to T1592 by the MITRE ATT&CK project.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-25195). If you want to get best quality of vulnerability data, you may have to visit 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: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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/08/2025 🔍
Sources
Vendor: google.comAdvisory: A-216854451
Status: Confirmed
CVE: CVE-2023-21027 (🔍)
GCVE (CVE): GCVE-0-2023-21027
GCVE (VulDB): GCVE-100-223834
EUVD: 🔍
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 03/25/2023 07:46Updated: 09/08/2025 05:09
Changes: 03/25/2023 07:46 (43), 04/14/2023 11:01 (11), 09/08/2025 05:09 (16)
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.