LiveActive security incident?Get immediate response
CVE Record

CVE-2023-20940: In the Android operating system, there is a possible way to replace a boot partition due to improperly used...

In the Android operating system, there is a possible way to replace a boot partition due to improperly used crypto. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-256237041

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Android 13 has a local privilege escalation flaw tied to improper cryptographic use that could allow a boot partition replacement. Successful exploitation could compromise device confidentiality, integrity, and availability. The issue is local and does not require user interaction, but public sources provided do not show active exploitation.

Executive priority

Treat as a high-priority mobile patching issue, especially for Android fleets handling sensitive data. It is not currently evidenced as actively exploited in the supplied sources, but the potential full-device impact justifies prompt remediation tracking.

Technical view

CVE-2023-20940 is a CWE-347 improper cryptographic verification issue in Android 13. The CVSS 3.1 score is 7.8 with local attack vector, low complexity, low privileges required, no user interaction, and high impact across confidentiality, integrity, and availability.

Likely exposure

Exposure is limited to Android 13 devices that have not received the relevant Android or OEM security update covering the February 2023 bulletin. Device build and security patch level determine practical exposure.

Exploitation context

The CVE describes local escalation of privilege with no user interaction. KEV status is false in the supplied bundle, and no cited source confirms exploitation in the wild. Public technical detail is limited.

Researcher notes

The record identifies the affected platform and impact but does not provide root-cause detail, exploit primitives, or patch diff context. Validation should rely on security patch level and OEM advisory mapping rather than assumptions about all Android 13 builds.

Mitigation direction

  • Review the Android February 2023 security bulletin and relevant OEM guidance.
  • Update affected Android 13 devices to a vendor build that includes the fix.
  • Verify managed devices meet minimum approved Android security patch levels.
  • Prioritize shared, BYOD, and high-privilege user devices for remediation.

Validation and detection

  • Inventory Android 13 devices across MDM, EDR, and asset systems.
  • Check each device security patch level against vendor guidance for CVE-2023-20940.
  • Confirm OEM builds explicitly include the Android February 2023 security bulletin content.
  • Review exceptions for unsupported devices or delayed carrier/OEM updates.
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-347: 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-20940 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-2023-20940Attack 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
n/aAndroidAndroid-13Listed
Weakness

CWE details

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

CWE-347 · source CWE mapping

Improper Verification of Cryptographic Signature

Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.