dbcve.org
YoctoApplication · Linuxfoundation

CVE-2024-20153

HIGH · 7.5 CVSS v3.1 Published 2025-01-06
Fix available
A fix is available. Upgrade to after 3.5 or later.
See remediation →
84/100
Remediation priority · High
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 STA, there is a possible way to trick a client to connect to an AP with spoofed SSID. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08990446 / ALPS09057442; Issue ID: MSV-1598.

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

This is a WLAN STA (client) vulnerability allowing an attacker to spoof an AP SSID, tricking the client into connecting to a malicious access point. This enables an evil twin attack for remote information disclosure. No user interaction or additional privileges are required for exploitation.

MitigationApply vendor patch ALPS08990446/ALPS09057442 to the affected WLAN STA firmware or driver. Until patched, users should verify network authenticity before connecting and avoid untrusted Wi-Fi networks.

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
YoctoApplication
Affected:= 3.3= 4.0= 5.0
Software Development KitApplication
Affected:<= 3.5
AndroidOperating system
Affected:= 14.0= 15.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your product and version
    Determine if your system runs Android, Yocto, or Mediatek SDK. For Android, go to Settings > About Phone > Android version. For Yocto, check the OS image version or /etc/VERSION. For Mediatek SDK, check the SDK release documentation or manifest file.
    Affected if The version matches Android 14.0 or 15.0, Yocto 3.3/4.0/5.0, or Mediatek SDK 3.5 or lower.
  2. Confirm WLAN STA (client) mode is enabled
    Check if Wi-Fi is enabled and the device is configured to connect to access points as a client. On Android, verify Wi-Fi is turned on. On embedded systems, check if wpa_supplicant or similar STA mode daemon is running.
    Affected if WLAN STA mode is active and the device connects to Wi-Fi networks.
  3. Check WLAN firmware or driver version
    On Android, use terminal or diagnostic tools to query the WLAN driver version (e.g., 'getprop ro.wlan.driver.version' or check Wi-Fi advanced settings). On Yocto/Mediatek, check /sys/class/net/wlan0/ or use 'iw version' and 'fwprintenv' to query firmware version.
    Affected if The WLAN firmware/driver version cannot be determined or is older than the patched versions containing ALPS08990446/ALPS09057442.
  4. Verify patch ALPS08990446 or ALPS09057442 is applied
    Check vendor release notes, kernel config, or WLAN driver changelog for presence of patches ALPS08990446 and ALPS09057442. Contact the device or chipset vendor to confirm patch inclusion.
    Affected if No documentation or vendor confirmation exists that these specific patches are included in the installed WLAN firmware or driver.

You are affected if your device runs one of the specified versions with WLAN STA mode enabled and the patches ALPS08990446/ALPS09057442 are not confirmed to be applied to your WLAN firmware or driver.

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.

From vendor data
Upgrade available Upgrade to a release after 3.5
Interim mitigation

Apply vendor patch ALPS08990446/ALPS09057442 to the affected WLAN STA firmware or driver. Until patched, users should verify network authenticity before connecting and avoid untrusted Wi-Fi networks.

Fix this in Yocto Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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