LiveActive security incident?Get immediate response
CVE Record

CVE-2022-20392: In declareDuplicatePermission of ParsedPermissionUtils.java, there is a possible way to obtain a dangerous...

In declareDuplicatePermission of ParsedPermissionUtils.java, there is a possible way to obtain a dangerous permission without user consent due to improper input validation. This could lead to local escalation of privilege during app installation or upgrade with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12LAndroid ID: A-213323615

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-20392 is an Android privilege escalation issue. During app installation or upgrade, an app may obtain a dangerous permission without the user's consent because permission input validation is flawed. This affects Android 10, 11, 12, and 12L. No source in the bundle shows active exploitation.

Executive priority

Treat this as a high-priority mobile fleet patching issue, especially where Android devices access sensitive business data or permit third-party app installation.

Technical view

The issue is in declareDuplicatePermission in ParsedPermissionUtils.java. Improper input validation may allow acquisition of a dangerous permission during install or upgrade. CVSS 3.1 is 7.8: local attack vector, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most relevant to fleets running Android 10, 11, 12, or 12L that have not received the Android September 2022 security bulletin fixes or OEM-equivalent updates.

Exploitation context

The CVE describes local escalation of privilege during app installation or upgrade. It requires low privileges and no user interaction. The provided sources do not cite public exploitation, proof-of-concept availability, or KEV listing.

Researcher notes

Evidence is limited to the CVE record and Android bulletin reference. The bundle does not include exploit details, patch diff analysis, or device-specific OEM status. Avoid assuming broader product impact beyond Android 10 through 12L.

Mitigation direction

  • Review the Android September 2022 security bulletin and OEM advisories.
  • Prioritize security updates for Android 10, 11, 12, and 12L devices.
  • Restrict installation from untrusted app sources where enterprise controls allow.
  • Use mobile device management to enforce minimum Android patch levels.
  • Monitor vendor guidance for device-specific update availability.

Validation and detection

  • Inventory Android versions across managed and supported devices.
  • Check each device security patch level against September 2022 or OEM equivalent.
  • Identify devices stuck on Android 10 through 12L without updates.
  • Review app installation policies and sideloading exposure.
  • Track exceptions where OEM patch status cannot be confirmed.
Prepared
Confidence
medium
Sources
3

Public sources used

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-20392 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2022-20392Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aAndroidAndroid-10 Android-11 Android-12 Android-12LListed
Weakness

CWE details

CWE-20

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