LiveActive security incident?Get immediate response
CVE Record

CVE-2023-20613: In ril, there is a possible out of bounds write due to a missing bounds check.

In ril, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07628614; Issue ID: ALPS07628614.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-20613 is a MediaTek radio interface layer flaw that can let a local, highly privileged attacker gain broader system-level control. It affects many MediaTek chipsets on Android 11, 12, and 13. No user interaction is required, but the attacker already needs high local privileges.

Executive priority

Treat this as a moderate mobile fleet hygiene issue, not an internet-wide emergency. Prioritize patch confirmation for managed Android devices with affected MediaTek chipsets, because successful exploitation can deepen compromise after an attacker already has high local privileges.

Technical view

The issue is an out-of-bounds write in ril caused by a missing bounds check, mapped to CWE-20. CVSS 3.1 is 6.7 with local access, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on Android devices using the listed MediaTek chipsets and Android 11.0, 12.0, or 13.0, especially where OEM firmware has not incorporated MediaTek patch ALPS07628614.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Exploitation is local and requires high privileges, reducing broad opportunistic risk, but successful exploitation could materially increase attacker control on an already-compromised device.

Researcher notes

The public description is concise and does not provide technical root-cause detail beyond ril, missing bounds check, and out-of-bounds write. Avoid assuming affected OEM models from chipset names alone; confirm through firmware advisories and patch provenance.

Mitigation direction

  • Confirm OEM firmware includes MediaTek patch ALPS07628614 or later February 2023 bulletin content.
  • Prioritize updates for affected MediaTek Android 11, 12, and 13 device fleets.
  • Check MediaTek and device OEM advisories for model-specific firmware availability.
  • Retire or isolate devices that cannot receive applicable OEM security updates.

Validation and detection

  • Inventory Android devices by MediaTek chipset model and Android major version.
  • Compare firmware build and security patch information against OEM release notes.
  • Verify whether patch ID ALPS07628614 is included in deployed firmware.
  • Track unsupported or unpatched devices as residual local privilege escalation risk.
Prepared
Confidence
high
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-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-2023-20613 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.7 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

6.7Medium
CVSS 3.1 vector shape for CVE-2023-20613Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:H/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
MediaTek, Inc.MT6739, MT6761, MT6762, MT6765, MT6768, MT6769, MT6771, MT6779, MT6781, MT6785, MT6789, MT6833, MT6853, MT6855, MT6873, MT6875, MT6877, MT6879, MT6883, MT6885, MT6889, MT6891, MT6893, MT6895, MT6983, MT8321, MT8385, MT8765, MT8766, MT8768, MT8786, MT8788, MT8789, MT8791, MT8791T, MT8797Android 11.0, 12.0, 13.0Listed
Weakness

CWE details

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

CWE-20 · source CWE mapping

Improper Input Validation

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