LiveActive security incident?Get immediate response
CVE Record

CVE-2022-20338: In HierarchicalUri.readFrom of Uri.java, there is a possible way to craft a malformed Uri object due to imp...

In HierarchicalUri.readFrom of Uri.java, there is a possible way to craft a malformed Uri object due to improper input validation. This could lead to a local escalation of privilege, preventing processes from validating URIs correctly, with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12LAndroid ID: A-171966843

LowCVSS 3.3Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2022-20338 is a low-severity Android issue where malformed URI data can interfere with URI validation. A local attacker with low privileges could gain limited privilege impact. The source bundle says no user interaction is required, but it does not indicate remote exploitation or broad system compromise.

Executive priority

Treat as routine mobile patch management, not an emergency. The business urgency is low unless many managed Android 11/12/12L devices remain behind on security updates or allow untrusted app installation.

Technical view

The flaw is improper input validation in HierarchicalUri.readFrom in Android Uri.java. Crafted malformed Uri objects may prevent processes from validating URIs correctly, leading to local escalation of privilege. CVSS 3.1 is 3.3: local attack vector, low complexity, low privileges, no user interaction, low integrity impact only.

Likely exposure

Exposure is limited to Android 11, Android 12, and Android 12L devices that have not received the relevant Android security update from Google or their OEM. Risk is mainly from local code already running on the device.

Exploitation context

The provided sources and KEV status do not show active exploitation. The vulnerability is local, requires low privileges, and does not require user interaction. The bundle provides no public exploit details and no evidence of network-based exploitation.

Researcher notes

The source bundle identifies CWE-20 and Android ID A-171966843, but does not provide patch diffs, proof-of-concept details, or affected OEM build ranges. Validate only against vendor advisories and device patch levels.

Mitigation direction

  • Check the Android May 2023 security bulletin and OEM guidance for applicable updates.
  • Prioritize patching managed Android 11, 12, and 12L devices.
  • Use MDM controls to enforce minimum Android security patch levels.
  • Restrict installation of untrusted local apps on affected devices.

Validation and detection

  • Inventory Android 11, 12, and 12L devices in managed fleets.
  • Verify each device security patch level against vendor guidance.
  • Confirm OEMs have shipped fixes for the affected device models.
  • Track exceptions for devices that cannot receive security updates.
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-2022-20338 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:N/I:L/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:N/I:L/A:N1.81.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/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-11 Android-12 Android-12LListed
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.