LiveActive security incident?Get immediate response
CVE Record

CVE-2023-20932: In onCreatePreferences of EditInfoFragment.java, there is a possible way to read contacts belonging to othe...

In onCreatePreferences of EditInfoFragment.java, there is a possible way to read contacts belonging to other users due to improper input validation. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12L Android-13Android ID: A-248251018

LowCVSS 3.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2023-20932 is a low-severity Android information disclosure issue. A local low-privileged actor could potentially read contacts belonging to another user on the same device without user interaction. The main business concern is privacy exposure on shared or multi-user Android devices, not system takeover.

Executive priority

Treat this as a privacy and compliance hygiene issue, not an emergency. Patch through normal mobile security update processes, with higher priority for shared devices or environments handling sensitive contact data.

Technical view

The issue is improper input validation in Android's EditInfoFragment.java onCreatePreferences path. It affects Android 10, 11, 12, 12L, and 13. CVSS 3.1 is 3.3, with local access, low complexity, low privileges, no user interaction, and low confidentiality impact only.

Likely exposure

Exposure is limited to affected Android 10 through 13 devices, especially shared, multi-user, or enterprise-managed devices where contacts are separated between users or profiles. The source bundle does not identify specific OEM builds or device models.

Exploitation context

The provided sources support only local exploitation with low privileges and no user interaction. The CVE is not marked as CISA KEV in the bundle, and no cited source reports active exploitation.

Researcher notes

Evidence points to CWE-20 improper input validation in EditInfoFragment.java. Validation should focus on whether patched builds prevent cross-user contact reads in the affected preference creation path. The bundle does not provide exploit details, commit links, or workaround specifics.

Mitigation direction

  • Apply the relevant Android February 2023 security update through the device OEM or carrier.
  • Check vendor advisories for device-specific patch availability and rollout timing.
  • Prioritize shared, kiosk, BYOD, and enterprise-managed Android devices first.
  • Limit untrusted local accounts or apps on devices until patched.

Validation and detection

  • Inventory Android 10, 11, 12, 12L, and 13 devices in scope.
  • Check each device's Android security patch level against vendor guidance.
  • Confirm OEM firmware includes the February 2023 Android bulletin fixes.
  • Review MDM compliance data for unpatched or unsupported devices.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-20932 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.3CVSS 3.1LowCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N1.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.3Low
CVSS 3.1 vector shape for CVE-2023-20932Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aAndroidAndroid-10 Android-11 Android-12 Android-12L Android-13Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.