CVE-2025-20690
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 read due to an incorrect bounds check. This could lead to local information disclosure with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00418038; Issue ID: MSV-3478.
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 confidenceOut of bounds read vulnerability in WLAN AP driver due to incorrect bounds check, allowing local information disclosure with user-level execution privileges but no user interaction required.
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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Check Mediatek SDK versionIdentify the installed Mediatek Software Development Kit version by reviewing SDK documentation, build artifacts, or system firmware information. Compare the version number against the affected range (<= 7.6.7.2).Affected if The installed Mediatek SDK version is 7.6.7.2 or lower.
-
Check Openwrt versionRun 'cat /etc/os-release' or 'opkg list-installed' to determine the exact Openwrt release version running on the device.Affected if The installed Openwrt version is exactly 19.07.0 or exactly 21.02.0.
-
Verify WLAN AP driver presenceCheck if the WLAN AP driver module is loaded or available on the system. This may involve examining kernel modules (lsmod), checking for wireless interface configurations (iwconfig/iw), or reviewing loaded network drivers.Affected if The WLAN AP driver (wireless AP functionality) is present and loaded on the system.
-
Confirm wireless AP interface configurationExamine the system's wireless configuration to determine if an access point (AP) mode interface is configured or active. Check hostapd configuration files, wireless config in /etc/config/wireless (Openwrt), or network interface listings for AP-type interfaces.Affected if A wireless access point interface is configured or active using the affected driver.
A system is affected if it runs Mediatek SDK <= 7.6.7.2 OR Openwrt 19.07.0/21.02.0 AND has the WLAN AP driver enabled with an active access point interface.
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 WCNCR00418038 to fix the bounds checking in the WLAN AP driver to prevent unauthorized information disclosure.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20690 — 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-20690 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