Cyber Resilience

CVE-2025-20633

Memory Safety in Mediatek Software Development Kit ≤ 7.4.0.1

Published
03 February 2025
Modified
18 March 2025
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0033 26th percentile
Risk Priority 63 floored blend · peak EPSS

Summary

CVE-2025-20633 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Mediatek Software Development Kit. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-20633 is a high-severity vulnerability in the WLAN Access Point (AP) driver, stemming from an incorrect bounds check that enables an out-of-bounds write. This flaw affects MediaTek's WLAN AP driver components, as detailed in their product security bulletin. Classified under CWE-787 (Out-of-bounds Write), it carries a CVSS v3.1 base score of 8.8 (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating significant impact potential.

An attacker positioned in the adjacent or proximal network segment (AV:A) can exploit this vulnerability remotely with low complexity, requiring no privileges (PR:N) or user interaction (UI:N). Successful exploitation leads to arbitrary code execution, granting high confidentiality, integrity, and availability impacts (C:H/I:H/A:H) without scope changes.

MediaTek's February 2025 Product Security Bulletin addresses the issue, providing Patch ID WCNCR00400889 for remediation. Affected vendors and device manufacturers should apply this patch to mitigate the risk of adjacent-network code execution.

EU & UK References

Vulnerability Data

In wlan AP driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to remote (proximal/adjacent) code execution with no additional execution privileges needed. User interaction is not needed for exploitation. Patch…

more

ID: WCNCR00400889; Issue ID: MSV-2491.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-20631Same product: Mediatek Mt7615
CVE-2025-20632Same product: Mediatek Mt7615
CVE-2024-20018Same product: Mediatek Mt7615
CVE-2025-20646Same product: Mediatek Mt7915
CVE-2024-20067Same vendor: Mediatek
CVE-2024-20131Same vendor: Mediatek
CVE-2025-20634Same vendor: Mediatek
CVE-2023-20819Same vendor: Mediatek
CVE-2023-32888Same vendor: Mediatek
CVE-2024-20133Same vendor: Mediatek

Affected Assets

mediatek
software development kit
≤ 7.4.0.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.

Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
prevents

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development and acceptance can detect and prevent out-of-bounds write defects.

prevents

Secure development life cycle mandates practices that prevent out-of-bounds writes.

prevents

Application security requirements can specify bounds-checking and safe memory handling.

prevents

Secure architecture and engineering principles reduce the likelihood of buffer overflows.

prevents

Secure coding directly addresses out-of-bounds writes through language choice and coding standards.

prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References