CVE-2024-20146
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 STA driver, there is a possible out of bounds write due to improper input validation. This could lead to remote (proximal/adjacent) code execution with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00389496 / ALPS09137491; Issue ID: MSV-1835.
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 confidenceA memory corruption vulnerability exists in the WLAN STA (Station) driver where improper input validation allows an out-of-bounds write. An attacker within wireless proximity can trigger this to achieve remote code execution without requiring any privileges or user interaction.
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= 3.3= 4.0= 5.0<= 2.5= 13.0= 14.0= 15.0= 23.05CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/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 the product and versionDetermine the exact OS/product version running on the device (e.g., Android build number, Yocto release, OpenWrt version, or Mediatek SDK version) and compare against the affected list: Yocto 3.3/4.0/5.0, Android 13.0/14.0/15.0, OpenWrt 23.05, or Mediatek SDK <= 2.5Affected if The installed version matches one of the affected versions listed in the CVE
-
Verify WLAN STA mode is enabledCheck if the device has a WiFi station (STA) interface configured and active. On Linux-based systems, use 'iwconfig' or 'ip link show' to list wireless interfaces and their mode. On Android, check via 'settings get global wifi_on' or by examining network interfacesAffected if A WLAN STA interface is present and enabled, making the driver code path executable
-
Confirm WiFi interface is activeVerify the wireless interface is up and connected or scanning. Use 'ip addr' or 'ifconfig' to check interface status, or 'wpa_cli status' if wpa_supplicant is runningAffected if The WiFi interface is in an up state and capable of transmitting/receiving wireless frames
-
Check driver or firmware versionIf accessible, query the wireless driver or firmware version. On Linux, check '/sys/class/net/wlan*/device/uevent' or use 'ethtool -i wlan0'. On Android, this may require root access via 'dmesg' or checking vendor-specific pathsAffected if The driver or firmware version cannot be determined or matches vulnerable revisions not yet patched
The environment is likely affected if running an affected product version with WLAN STA mode enabled and an active WiFi interface, allowing an attacker within wireless proximity to trigger the memory corruption.
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 the vendor patch (WCNCR00389496/ALPS09137491) through system or driver updates. Prioritize patching on devices with exposed WiFi interfaces in high-density wireless environments.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20146 — 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-2024-20146 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