dbcve.org
Software Development KitApplication · Mediatek

CVE-2025-20712

HIGH · 8.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to after 8.3.1.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) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00422323; Issue ID: MSV-3810.

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

Memory corruption vulnerability in WLAN AP driver where an incorrect bounds check allows an out-of-bounds write operation. This enables remote adjacent attackers to escalate privileges without requiring user interaction or additional execution privileges.

MitigationApply vendor patch WCNCR00422323 to affected WLAN AP devices. If immediate patching is not feasible, restrict physical/proximal access to wireless networks and implement network segmentation 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:<= 8.3.1.1
OpenwrtOperating system
Affected:= 21.02.0= 23.05

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 Mediatek WLAN hardware in use
    Check system information or wireless driver details (e.g., 'lspci' for PCIe, 'lsusb' for USB, or check /proc/bus/pci/devices). Look for Mediatek or MTK wireless chipsets such as MT7621, MT7915, MT7921, etc.
    Affected if Device uses Mediatek WLAN hardware and the WLAN AP driver is loaded
  2. Confirm WLAN AP mode is enabled
    Check wireless configuration files or running services. On OpenWrt, use 'uci show wireless' or check /etc/config/wireless. Look for 'mode AP' or 'interface mode AP' in the wireless configuration.
    Affected if WLAN AP (Access Point) mode is actively configured and running - the vulnerability is in the AP driver specifically
  3. Check Mediatek SDK version
    Examine firmware or system image details. Check /etc/version, /etc/*release*, or vendor firmware metadata. Look for SDK version strings like 'SDK version 8.x.x' or check 'cat /proc/version' if available.
    Affected if Mediatek SDK version is <= 8.3.1.1
  4. Check OpenWrt version
    Run 'cat /etc/openwrt_version' or 'cat /etc/os-release' or check 'uname -a' output for the version string.
    Affected if OpenWrt version is exactly 21.02.0 or 23.05 and uses Mediatek WLAN drivers

A user is affected if they are running Mediatek SDK <= 8.3.1.1 or OpenWrt 21.02.0/23.05 on hardware with Mediatek WLAN chipsets, with WLAN AP mode enabled.

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 8.3.1.1
Interim mitigation

Apply vendor patch WCNCR00422323 to affected WLAN AP devices. If immediate patching is not feasible, restrict physical/proximal access to wireless networks and implement network segmentation to limit attack surface.

Recommended fix Moderate confidence

MediaTek SDK > 8.3.1.1 or OpenWrt version newer than 23.05 that includes the patched wlan AP driver

  1. 1. Identify the MediaTek SDK version in use by checking your device firmware or build system
  2. 2. Obtain the updated MediaTek SDK version that includes the fix for patch WCNCR00422323
  3. 3. For OpenWrt users: Update to a newer OpenWrt release that incorporates the patched MediaTek WLAN driver (version 21.02.0 and 23.05 are specifically listed as affected)
  4. 4. Rebuild the firmware with the updated SDK
  5. 5. Deploy the updated firmware to affected devices
  6. 6. Verify the WLAN driver version after deployment to confirm the patch is applied
Caveat Upgrading SDK versions may introduce compatibility changes with existing configurations or require adjustment of wireless settings; test thoroughly in a staging environment before production deployment

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

Fix this in Software Development Kit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
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,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-20712 — 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-20712 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