LiveActive security incident?Get immediate response
CVE Record

CVE-2022-20350: In onCreate of NotificationAccessConfirmationActivity.java, there is a possible way to trick the victim to...

In onCreate of NotificationAccessConfirmationActivity.java, there is a possible way to trick the victim to grant notification access to the wrong app due to improper input validation. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12LAndroid ID: A-228178437

MediumCVSS 6.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-20350 is an Android flaw that could let a local attacker cause notification access to be granted to the wrong app. That access can expose sensitive notification content. The issue affects Android 10, 11, 12, and 12L, and was addressed in Android’s August 2022 security bulletin.

Executive priority

Treat as a moderate mobile privacy risk. It is not cited as actively exploited, but notification access can expose sensitive business messages, MFA prompts, and personal data on unpatched Android devices.

Technical view

The source describes improper input validation in NotificationAccessConfirmationActivity.onCreate. The vulnerability can result in local information disclosure with no required privileges or user interaction under CVSS v3.1, although the narrative also says user execution privileges are needed. Confidentiality impact is rated high; integrity and availability are not impacted.

Likely exposure

Exposure is most likely on Android 10 through 12L devices missing the August 2022 Android security update or equivalent OEM patch level.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The CVSS vector is local, low complexity, no privileges, no user interaction, with high confidentiality impact.

Researcher notes

Evidence is limited to CVE metadata and the Android bulletin reference. The listed CWE-125 does not neatly match the described notification permission confusion, so validation should rely on Android patch status and advisory details rather than CWE interpretation alone.

Mitigation direction

  • Apply Android August 2022 security updates or later OEM security patches.
  • Prioritize Android 10, 11, 12, and 12L devices below the fixed patch level.
  • Check vendor or OEM guidance for device-specific patch availability.
  • Restrict notification access to trusted apps through device policy where possible.
  • Remove unknown or unnecessary apps with notification listener access.

Validation and detection

  • Inventory Android OS versions and security patch levels across managed devices.
  • Confirm affected devices report August 2022 security patch level or later.
  • Review notification access settings for unexpected or untrusted apps.
  • Verify OEM release notes map the device build to the Android August 2022 bulletin.
  • Document exceptions where unsupported devices cannot receive vendor fixes.
Prepared
Confidence
medium
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-125: 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-20350 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
Medium
CVSS
6.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/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
6.2CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N2.53.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.2Medium
CVSS 3.1 vector shape for CVE-2022-20350Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/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

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 links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.