LiveActive security incident?Get immediate response
CVE Record

CVE-2022-32624: In throttling, there is a possible out of bounds write due to an incorrect calculation of buffer size.

In throttling, there is a possible out of bounds write due to an incorrect calculation of buffer size. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07405923; Issue ID: ALPS07405923.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-32624 is a MediaTek Android firmware flaw where a buffer size is calculated incorrectly, allowing a local out-of-bounds write. The reported impact is local privilege escalation, with no user interaction required. It is not a remote internet-facing issue in the provided sources.

Executive priority

Handle this as a firmware patch management issue for affected Android fleets. It has serious local impact but no sourced evidence of remote exploitation or active exploitation. Prioritize devices with sensitive access or long patch delays.

Technical view

The issue is in MediaTek throttling logic and maps to CWE-131. Affected chipsets are MT6789, MT6855, MT6895, MT6983, MT8168, MT8365, and MT8781 on Android 11.0 or 12.0. CVSS 3.1 is 6.7: local attack vector, low complexity, high privileges required, no UI, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to Android devices using the listed MediaTek chipsets and affected Android versions. Asset owners usually need OEM model and firmware details to confirm whether the MediaTek patch is present.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. The vulnerability is local, requires high privileges per CVSS, and does not require user interaction. No exploit details are provided in the cited sources.

Researcher notes

Evidence is concise and vendor-centered. The sources identify affected MediaTek chipsets, Android versions, CWE-131, CVSS, and patch identifier, but do not provide detailed root-cause analysis, exploit maturity, or OEM-specific fixed build numbers.

Mitigation direction

  • Check MediaTek and device OEM guidance for Patch ID ALPS07405923.
  • Apply OEM firmware or Android security updates that include the MediaTek fix.
  • Prioritize managed devices with affected MediaTek chipsets on Android 11 or 12.
  • Restrict high-privilege local access on affected devices until patched.

Validation and detection

  • Inventory Android devices by chipset, model, Android version, and firmware build.
  • Confirm whether each OEM build includes MediaTek Patch ID ALPS07405923.
  • Review MDM or EDR data for affected Android 11 and 12 devices.
  • Track remediation status separately for each OEM firmware branch.
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-131: 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-32624 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-32624Attack 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.MT6789, MT6855, MT6895, MT6983, MT8168, MT8365, MT8781Android 11.0, 12.0Listed
Weakness

CWE details

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

CWE-131 · source CWE mapping

Incorrect Calculation of Buffer Size

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