CVE-2025-20719
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 · uneditedIn 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: WCNCR00418955; Issue ID: MSV-3570.
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 · moderate confidenceA bounds check error in the WLAN AP driver causes an out-of-bounds memory write vulnerability, allowing a proximal/adjacent attacker to achieve escalation of privileges without requiring user interaction or additional execution privileges.
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<= 7.6.7.2= 19.07.0= 21.02.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Mediatek SDK versionLocate the Mediatek Software Development Kit installation directory and check the SDK version file or use 'cat /etc/version' or check firmware metadata for version string like 7.6.7.2Affected if The installed Mediatek SDK version is 7.6.7.2 or lower
-
Identify OpenWrt versionRun 'cat /etc/os-release' or check '/etc/openwrt_version' to obtain the exact OpenWrt release versionAffected if The OpenWrt version is exactly 19.07.0 or 21.02.0
-
Confirm WLAN AP functionality is in useCheck if the device is configured as a wireless access point by examining network configuration files, running 'iwconfig' or 'ip link show' for wireless interfaces, or reviewing AP mode settingsAffected if WLAN AP mode is enabled and the system is acting as a wireless access point using Mediatek hardware or the affected OpenWrt versions
-
Verify Mediatek wireless hardware or driver is presentCheck system hardware info or wireless driver modules for Mediatek chipsets using commands like 'lspci', 'lsusb', 'lsmod', or by inspecting '/proc/net/wireless' for Mediatek device identifiersAffected if The system contains Mediatek wireless hardware and uses the affected WLAN AP driver
A system is affected if it runs Mediatek SDK version 7.6.7.2 or lower, or OpenWrt 19.07.0 or 21.02.0, and has an active WLAN AP configuration using Mediatek wireless hardware.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor patch WCNCR00418955 to affected WLAN AP drivers. Until patch deployment is feasible, limit physical/proximal access to wireless infrastructure and monitor for unauthorized device associations.
- Consultation6.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20719 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-20719 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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