LiveActive security incident?Get immediate response
CVE Record

CVE-2023-20927: In permissions of AndroidManifest.xml, there is a possible way to grant signature permissions due to a perm...

In permissions of AndroidManifest.xml, there is a possible way to grant signature permissions due to a permissions bypass. 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-244216503

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-20927 is an Android 13 privilege-escalation issue. A locally installed or executing low-privilege app could bypass permission restrictions and gain signature-level permissions, potentially exposing sensitive data, integrity, and availability.

Executive priority

Treat this as high priority for Android 13 fleets because successful exploitation could turn limited local access into powerful system permissions. It is not a confirmed internet-scale or actively exploited issue from the supplied evidence.

Technical view

The issue is a CWE-284 permissions bypass in AndroidManifest.xml permissions handling. CVSS 3.1 is 7.8: local attack vector, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to Android 13 builds that have not received the relevant vendor security update referenced by the Android February 2023 AAOS bulletin. Public sources do not identify other affected products or versions.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. Exploitation is local and requires some existing low-privilege execution on the device, but no user interaction.

Researcher notes

Public detail is sparse. The useful facts are permission bypass, signature-permission grant risk, Android 13 scope, no user interaction, and local low-privilege prerequisites. Avoid assuming a specific vulnerable component beyond the AndroidManifest.xml permissions description.

Mitigation direction

  • Apply the relevant Android or OEM security update for affected Android 13 builds.
  • Check vendor firmware guidance for device-specific patch availability and rollout timing.
  • Prioritize managed fleets, shared devices, and vehicles using Android Automotive OS.
  • Restrict untrusted app installation where enterprise controls allow it.

Validation and detection

  • Inventory Android 13 devices and firmware builds in scope.
  • Confirm security patch levels include the referenced February 2023 Android fix.
  • Verify OEM advisories map the fix to deployed device models.
  • Review MDM telemetry for outdated or unmanaged Android 13 devices.
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 · medium confidence lookup

CWE-284: 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-20927 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-20927Attack 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-284 · source CWE mapping

Improper Access Control

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