LiveActive security incident?Get immediate response
CVE Record

CVE-2023-21245: In showNextSecurityScreenOrFinish of KeyguardSecurityContainerController.java, there is a possible way to a...

In showNextSecurityScreenOrFinish of KeyguardSecurityContainerController.java, there is a possible way to access the lock screen during device setup due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-21245 is an Android lock-screen/setup flaw. A local attacker with some device access could potentially bypass intended setup or lock-screen protections and gain elevated privileges. Google rated it high severity. The supplied sources do not show active exploitation.

Executive priority

Treat this as a high-priority mobile fleet patching issue, not an internet-facing emergency. The main business risk is unauthorized local privilege escalation on unpatched Android devices, especially shared or provisioned endpoints.

Technical view

The issue is a CWE-863 authorization logic error in KeyguardSecurityContainerController.showNextSecurityScreenOrFinish. Google lists Android 11, 12, 12L, and 13 as affected. CVSS 3.1 is 7.8 with local attack vector, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on Android 11, 12, 12L, or 13 devices missing the July 2023 Android security update or equivalent OEM patch. Risk is local, so shared, kiosk, managed, or physically accessible devices deserve priority.

Exploitation context

The supplied CVE data says exploitation requires local access and low privileges, with no user interaction. CISA KEV status is false in the bundle, and no supplied source confirms active exploitation. Do not assume remote exploitation from this evidence.

Researcher notes

Evidence points to a Keyguard setup-state authorization flaw fixed in AOSP frameworks/base and documented in the Android July 2023 bulletin. The public bundle does not provide exploit details, exploitation evidence, or separate mitigations beyond applying vendor updates.

Mitigation direction

  • Apply the July 2023 Android security update or equivalent OEM firmware update.
  • Prioritize affected Android 11, 12, 12L, and 13 devices.
  • Check vendor or carrier guidance for device-specific patch availability.
  • Replace or isolate unsupported devices that cannot receive security updates.
  • For AOSP builds, include the referenced frameworks/base fix.

Validation and detection

  • Inventory Android device versions and security patch levels.
  • Confirm whether Android 11, 12, 12L, or 13 devices remain unpatched.
  • Verify OEM advisories map the installed update to CVE-2023-21245.
  • For custom builds, confirm the referenced AOSP commit is present.
  • Review managed-device enrollment and setup workflows for unpatched devices.
Prepared
Confidence
high
Sources
4

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 · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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-21245 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
3Source 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-2023-21245Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid13, 12L, 12, 11unaffected
Weakness

CWE details

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

CWE-863 · source CWE mapping

Incorrect Authorization

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