dbcve.org
Iot YoctoApplication · Mediatek

CVE-2024-20100

CRITICAL · 9.8 CVSS v3.1 Published 2024-10-07
Fix available
A fix is available. Upgrade to after 3.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 driver, there is a possible out of bounds write due to improper input validation. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08998449; Issue ID: MSV-1603.

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 driver allows an out-of-bounds write due to improper input validation. This can be exploited for remote code execution without requiring any user interaction or additional privileges, making it highly dangerous in networked environments.

MitigationApply the vendor patch (ALPS08998449) immediately given the critical severity (CVSS 9.8) and the fact that exploitation requires no user interaction or 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
Iot YoctoApplication
Affected:= 24.0
Software Development KitApplication
Affected:<= 3.3
AndroidOperating system
Affected:= 12.0= 13.0= 14.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 the Android version
    Check system settings 'About phone' or run 'getprop ro.build.version.release' in adb shell
    Affected if Android version is exactly 12.0, 13.0, or 14.0 with a Mediatek chipset
  2. Identify the Mediatek SDK version
    Check the SDK installation directory for version metadata, or run 'grep -r VERSION' in the SDK root directory, or check the SDK release notes file
    Affected if SDK version is 3.3 or lower
  3. Identify the Mediatek Iot Yocto version
    Check the Yocto build environment for the OS version: run 'cat /etc/VERSION' or check the build configuration 'conf/local.conf' for the image version
    Affected if Yocto version is exactly 24.0
  4. Confirm Mediatek WLAN hardware is present
    Check WLAN interface exists: run 'ip link show' or 'iw dev' in terminal, or check 'getprop ro.wlan.mtk' in adb shell on Android
    Affected if A Mediatek WLAN interface is present and active
  5. Check Mediatek WLAN driver module version
    Run 'modinfo wlanz' or check '/sys/class/net/wlan0/device/driver/version' if the driver is loaded, or inspect the WiFi firmware version via 'getprop ro.wlan.fw'
    Affected if Driver or firmware version cannot be determined or is unknown

You are affected if you are running Mediatek Iot Yocto 24.0, Mediatek SDK 3.3 or lower, or Android 12.0/13.0/14.0 on hardware with a Mediatek WLAN driver, and the vendor patch ALPS08998449 has not been applied.

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

Apply the vendor patch (ALPS08998449) immediately given the critical severity (CVSS 9.8) and the fact that exploitation requires no user interaction or privileges.

Recommended fix Moderate confidence
  1. Contact MediaTek directly to obtain patch ALPS08998449 for this WLAN driver vulnerability
  2. Apply the vendor-supplied patch to the affected IoT Yocto 24.0, SDK versions <=3.3, and Android 12.0/13.0/14.0 installations
  3. After patching, verify the wlan driver version reflects the security update
  4. For Android devices, apply the latest MediaTek-supplied security patch level from your device OEM

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

Fix this in Iot Yocto Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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