Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-20140: CWE-787 Out-of-bounds Write in MediaTek, Inc. MT6739, MT6761, MT6768, MT6781, MT6833, MT6853, MT6877, MT6885, MT6893, MT8518S, MT8532

0
Medium
VulnerabilityCVE-2024-20140cvecve-2024-20140cwe-787
Published: Mon Jan 06 2025 (01/06/2025, 03:17:43 UTC)
Source: CVE Database V5
Vendor/Project: MediaTek, Inc.
Product: MT6739, MT6761, MT6768, MT6781, MT6833, MT6853, MT6877, MT6885, MT6893, MT8518S, MT8532

Description

In power, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS09270402; Issue ID: MSV-2020.

AI-Powered Analysis

AILast updated: 02/26/2026, 21:34:15 UTC

Technical Analysis

CVE-2024-20140 is a medium severity vulnerability classified under CWE-787 (Out-of-bounds Write) affecting a range of MediaTek system-on-chip (SoC) models widely used in mobile and embedded devices. The flaw exists in the power management component where a missing bounds check leads to an out-of-bounds write condition. This memory corruption can be exploited by a local attacker who already has System-level privileges to escalate their privileges further, potentially gaining unauthorized control over sensitive system functions. The vulnerability does not require user interaction, making it more straightforward to exploit once the attacker has the necessary access. Affected platforms include Android versions 12 through 15 and Yocto Linux versions 3.3 to 5.0 running on the specified MediaTek SoCs. The CVSS 3.1 vector (AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H) indicates that the attack requires local access with high privileges but can cause high impact on confidentiality, integrity, and availability. Although no public exploits are known, the vulnerability poses a significant risk in environments where attackers can gain System privileges, such as through other chained exploits or insider threats. The issue was reserved in November 2023 and published in January 2025, with patches presumably forthcoming from MediaTek (patch ID ALPS09270402).

Potential Impact

The vulnerability allows an attacker with existing System privileges to perform an out-of-bounds write, potentially leading to arbitrary code execution or system compromise at a higher privilege level. This can result in unauthorized access to sensitive data, disruption of device operations, or persistent control over affected devices. Since the affected chipsets are commonly used in smartphones, IoT devices, and embedded systems, the impact spans consumer, enterprise, and industrial sectors. Organizations relying on devices with these MediaTek SoCs may face risks of privilege escalation attacks that could bypass security controls, leading to data breaches or operational disruptions. The requirement for prior System privileges limits the initial attack surface but does not eliminate risk, especially in scenarios involving multi-stage attacks or insider threats. The lack of user interaction needed for exploitation increases the threat in automated or unattended environments.

Mitigation Recommendations

1. Apply official patches from MediaTek or device manufacturers as soon as they become available to address the missing bounds check. 2. Implement strict privilege separation and minimize the number of processes or users with System-level privileges to reduce the risk of privilege escalation. 3. Employ runtime protections such as memory safety enforcement, bounds checking, and exploit mitigation techniques (e.g., Control Flow Integrity, Address Space Layout Randomization) where supported. 4. Monitor system logs and behaviors for anomalies indicative of out-of-bounds memory writes or privilege escalation attempts. 5. Conduct regular security assessments and penetration testing focusing on privilege escalation vectors in devices using affected MediaTek SoCs. 6. For embedded and IoT deployments, ensure secure boot and firmware integrity checks to prevent unauthorized code execution. 7. Educate developers and system integrators about secure coding practices to avoid similar vulnerabilities in custom components interfacing with MediaTek hardware.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
MediaTek
Date Reserved
2023-11-02T13:35:35.183Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69a0a43c85912abc71d620cf

Added to database: 2/26/2026, 7:51:24 PM

Last enriched: 2/26/2026, 9:34:15 PM

Last updated: 2/26/2026, 11:17:43 PM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses