dbcve.org
YoctoApplication · Linuxfoundation

CVE-2023-20691

HIGH · 7.5 CVSS v3.1 Published 2023-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 firmware, there is possible system crash due to an integer overflow. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS07664731; Issue ID: ALPS07664731.

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 vulnerability exists in WLAN firmware where an integer overflow condition can be triggered, leading to a system crash. The flaw is remotely exploitable without requiring any user interaction or elevated privileges, making it easily weaponizable for denial of service attacks.

MitigationApply the vendor-provided firmware patch (ALPS07664731) to affected devices. Given this is a firmware-level integer overflow, network-based workarounds cannot reliably prevent exploitation and patching is the definitive remediation.

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:= 4.0
AndroidOperating system
Affected:= 11.0= 12.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 your operating system and version
    On Android, go to Settings > About Phone > Android version. On Yocto-based systems, run 'cat /etc/os-release' or check the build manifest.
    Affected if The system runs Android 11.0, Android 12.0, or Linuxfoundation Yocto version 4.0
  2. Confirm WLAN hardware is present and enabled
    On Android, check Settings > Network & Internet > Wi-Fi is turned on. On Linux, run 'iw dev' or check 'ip link show' for wireless interfaces.
    Affected if WLAN hardware is present and the wireless interface is active
  3. Check WLAN firmware version
    On Android, this information is typically not directly user-accessible but may appear in kernel logs (dmesg) or under Settings > About Phone > SIM status > ICCID. On Linux Yocto systems, check '/lib/firmware/' directory for wireless firmware files or run 'cat /sys/class/net/wlan0/device/firmware_version' if available.
    Affected if Unable to verify firmware version but running affected OS versions with WLAN enabled puts the system in potential risk range
  4. Review system crash logs for WLAN-related crashes
    Check Android logs via 'adb logcat -d' or Bugreport for entries containing 'WLAN', 'firmware', or crash timestamps. On Yocto, check 'journalctl' or '/var/log/messages' for similar entries.
    Affected if Recent system crashes or reboots correlate with WLAN activity on affected OS versions

A system is likely affected if it runs Android 11.0 or 12.0 or Yocto 4.0, has WLAN functionality enabled, and is experiencing unexplained crashes or stability issues.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-provided firmware patch (ALPS07664731) to affected devices. Given this is a firmware-level integer overflow, network-based workarounds cannot reliably prevent exploitation and patching is the definitive remediation.

Recommended fix Moderate confidence
  1. Contact the device/hardware manufacturer to obtain the updated WLAN firmware containing patch ALPS07664731
  2. For Android devices, apply the latest system updates from the device vendor which bundle the MediaTek firmware fix
  3. For Yocto-based systems, rebuild the system image with the latest MediaTek WLAN firmware package available in the vendor's layer or meta-firmware layer
  4. Verify the firmware version post-update matches a version that includes the ALPS07664731 patch
Caveat Firmware updates may require device reboot and should be tested in a staging environment first

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

Fix this in Yocto Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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