dbcve.org
Software Development KitApplication · Mediatek

CVE-2025-20633

HIGH · 8.8 CVSS v3.1 Published 2025-02-03
Fix available
A fix is available. Upgrade to after 7.4.0.1 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 ID: WCNCR00400889; Issue ID: MSV-2491.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in the WLAN AP driver allows an attacker in proximal/adjacent range to trigger an out-of-bounds write due to an incorrect bounds check, potentially achieving remote code execution without requiring any privileges or user interaction.

MitigationApply the vendor patch (WCNCR00400889) to the WLAN AP driver firmware. Restrict physical/proximal access to WLAN networks and segment wireless infrastructure to limit attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Software Development KitApplication
Affected:<= 7.4.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Mediatek SDK is in use
    Review your device firmware or build documentation to determine if the system incorporates Mediatek Software Development Kit components. Check firmware bills of materials or dependency listings for Mediatek SDK packages.
    Affected if The device or firmware uses Mediatek Software Development Kit components.
  2. Determine the Mediatek SDK version
    Locate the SDK version information in your firmware build artifacts, release notes, or system documentation. Common locations include build configuration files, SDK release manifests, or version metadata files included with the firmware.
    Affected if The installed SDK version is 7.4.0.1 or earlier.
  3. Verify WLAN AP driver is present and active
    Inspect the loaded kernel modules or firmware components to confirm the Mediatek WLAN AP driver is included in the system build. Check if the wireless access point functionality is configured or running.
    Affected if The Mediatek WLAN AP driver is present in the system and the WLAN AP feature is enabled.
  4. Confirm wireless AP functionality is in use
    Examine system network configuration to determine if the device is operating as a wireless access point or if wireless AP interfaces are active. Review wireless interface status and configuration settings.
    Affected if The device is actively functioning as a WLAN access point using the affected driver.

A system is affected if it runs Mediatek SDK version 7.4.0.1 or earlier AND has the WLAN AP driver enabled and operational as a wireless access point.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 7.4.0.1
Interim mitigation

Apply the vendor patch (WCNCR00400889) to the WLAN AP driver firmware. Restrict physical/proximal access to WLAN networks and segment wireless infrastructure to limit attack surface.

Recommended fix Moderate confidence

Contact MediaTek (corp.mediatek.com) for the fixed SDK version beyond 7.4.0.1 (patch ID WCNCR00400889)

  1. 1. Identify all MediaTek SDK deployments in your environment that use version 7.4.0.1 or earlier
  2. 2. Contact MediaTek directly through their official support channels or security team to obtain the fixed SDK version
  3. 3. Request the specific fixed release for patch ID WCNCR00400889 / Issue ID MSV-2491
  4. 4. Before deploying the update, test the fixed SDK version in a staging environment to ensure compatibility
  5. 5. Deploy the upgraded SDK to production systems following your standard change management process
  6. 6. Verify that the wlan AP driver component has been successfully updated and is functioning correctly
Caveat Check MediaTek release notes for any API or compatibility changes between 7.4.0.1 and the fixed version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Software Development Kit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20633 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-20633 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data