LiveActive security incident?Get immediate response
CVE Record

CVE-2022-32620: In mpu, there is a possible memory corruption due to a logic error.

In mpu, there is a possible memory corruption due to a logic error. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07541753; Issue ID: ALPS07541753.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-32620 is a MediaTek MPU memory corruption flaw affecting listed chipsets on Android 11, 12, and 13. It requires local high privileges, but successful exploitation could affect confidentiality, integrity, and availability with System-level impact. No active exploitation is stated in the provided sources.

Executive priority

Treat this as a targeted endpoint firmware risk, not an emergency internet-facing issue. Patch through normal mobile device management cycles, with higher priority for privileged, shared, or unsupported Android devices.

Technical view

The flaw is described as a logic-error memory corruption issue in MediaTek mpu, mapped to CWE-787. CVSS 3.1 is 6.7: local attack vector, low complexity, high privileges required, no user interaction, unchanged scope, and high CIA impact. MediaTek references patch ID ALPS07541753.

Likely exposure

Exposure is likely limited to Android devices using MediaTek MT6781, MT6789, MT6833, MT6853, MT6873, MT6877, MT8781, or MT8791 on Android 11 through 13.

Exploitation context

The source data does not show internet exposure or remote exploitation. An attacker would need local high privileges first, then could potentially escalate or corrupt MPU-related memory. CISA KEV status is false in the bundle.

Researcher notes

Evidence is sparse: the bundle names the affected chipsets, Android versions, CWE, CVSS vector, and MediaTek patch ID, but does not provide root-cause detail, exploitability proof, or product-specific fixed build numbers.

Mitigation direction

  • Identify devices using the listed MediaTek chipsets and Android versions.
  • Apply OEM firmware or Android updates that include MediaTek patch ALPS07541753.
  • Check MediaTek and device-vendor advisories for product-specific update guidance.
  • Prioritize managed or shared devices where local high-privilege access is plausible.
  • Retire or isolate affected devices that cannot receive vendor-supported updates.

Validation and detection

  • Map device models to MediaTek chipset identifiers in asset inventory.
  • Confirm Android versions are not 11, 12, or 13 unless patched.
  • Review OEM release notes for MediaTek December 2022 bulletin coverage.
  • Verify patch level or firmware build includes ALPS07541753 where documented.
  • Track exceptions for unsupported devices until replacement or isolation.
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-787: 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-32620 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-2022-32620Attack 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.MT6781, MT6789, MT6833, MT6853, MT6873, MT6877, MT8781, MT8791Android 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-787 · source CWE mapping

Out-of-bounds Write

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