YoctoApplication · Linuxfoundation

CVE-2023-20690

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: ALPS07664735; Issue ID: ALPS07664735.

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 confidence

An integer overflow vulnerability exists in the WLAN firmware that allows remote attackers to cause a system crash, resulting in denial of service. The vulnerability can be exploited without requiring user interaction or additional execution privileges.

MitigationApply the vendor patch (ALPS07664735) by updating the WLAN firmware to the patched version. If a patch is unavailable, consider network segmentation to limit exposure of affected WLAN components.

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 the WLAN firmware version
    Check the device or system for WLAN firmware version. On Android, this may be in Settings > About Phone > Wi-Fi MAC address or through vendor-specific diagnostic tools. On Yocto-based systems, check /lib/firmware or use commands like 'iw list' or 'rfkill list' to identify the firmware version file or driver information.
    Affected if The WLAN firmware version matches the Android 11.0 or 12.0 builds, or the Yocto 4.0 build, and the vendor has not applied patch ALPS07664735.
  2. Determine the baseband or WLAN chip firmware
    Query the WLAN driver or firmware subsystem. On Linux/Yocto systems, examine /sys/class/net/*/device/firmware_version or check dmesg for firmware loading messages. On Android, use 'adb shell getprop' to query ro.wlan.firmware.version or similar properties.
    Affected if The displayed firmware version corresponds to the unpatched version for Android 11.0, Android 12.0, or Yocto 4.0.
  3. Confirm the product version
    Verify the installed operating system version. On Android, go to Settings > About Phone > Android version. On Yocto-based devices, check the OS build information using 'cat /etc/os-release' or 'uname -a'.
    Affected if The system runs Android 11.0, Android 12.0, or Linuxfoundation Yocto 4.0 exactly.
  4. Check for vendor firmware updates
    Contact the device manufacturer or check the vendor support site for firmware release notes related to CVE-2023-20690 or patch ALPS07664735. Look for WLAN firmware updates released after the CVE disclosure date.
    Affected if No firmware update addressing this CVE has been applied, and the product version matches the affected versions.

A user is affected if their device runs Android 11.0 or Android 12.0, or Linuxfoundation Yocto 4.0, and the WLAN firmware has not been updated to include the patch ALPS07664735.

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

Apply the vendor patch (ALPS07664735) by updating the WLAN firmware to the patched version. If a patch is unavailable, consider network segmentation to limit exposure of affected WLAN components.

Fix this in Yocto Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-20690 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