dbcve.org
YoctoApplication · Linuxfoundation

CVE-2024-20023

MEDIUM · 6.7 CVSS v3.1 Published 2024-03-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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 flashc, there is a possible out of bounds write due to lack of valudation. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08541638; Issue ID: ALPS08541638.

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

A memory corruption vulnerability in the flashc (flash controller) component allows an attacker with System-level privileges to perform an out-of-bounds write due to insufficient input validation, enabling local privilege escalation without user interaction.

MitigationApply the vendor patch ALPS08541638 which adds proper validation to prevent the out-of-bounds write condition in the flashc component. Since this is a local privilege escalation requiring System privileges, ensure patch deployment follows standard change management procedures.

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
Rdk BApplication
Affected:= 2022q3
AndroidOperating system
Affected:= 12.0= 13.0= 14.0
OpenwrtOperating system
Affected:= 19.07.0= 21.02.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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 installed product and version
    Determine which of the affected products (Yocto, RDK B, Android, or OpenWrt) is running in your environment, then run the appropriate command to check the version: for Yocto check /etc/os-release or 'cat /etc/version', for RDK B check the firmware version, for Android check 'getprop ro.build.version.release', for OpenWrt check 'cat /etc/os-release' or 'opkg list-installed'
    Affected if The installed version matches 3.3 for Yocto, 2022q3 for RDK B, 12.0/13.0/14.0 for Android, or 19.07.0/21.02.0 for OpenWrt
  2. Verify the flashc component is present
    Check if the flashc (flash controller) driver or module is loaded on the system. On Linux-based systems this may appear in 'lsmod', '/proc/modules', or as a kernel driver. On Android check /dev/ or kernel config for flash controller support.
    Affected if The flashc component is loaded, enabled, or present in the system firmware
  3. Confirm current privilege level
    Check the privilege context of the potential attack vector: on Android verify if the process runs with SYSTEM privileges (check via 'ps -A | grep <process>' and 'dumpsys activity activities' if relevant), on Linux check if user is root or has equivalent System privileges via 'id' or 'whoami'
    Affected if The attacker already possesses System-level or root privileges on the target device
  4. Review system audit or security logs for exploitation indicators
    Search system logs (/var/log, dmesg, logcat on Android) for any unexpected flash controller access, memory corruption errors, or privilege escalation activity related to flashc
    Affected if Logs show unexplained out-of-bounds memory writes or flashc-related crashes

You are affected if your system runs one of the listed versions AND has the flashc component enabled AND an attacker already has System-level access to attempt the privilege escalation.

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 ALPS08541638 which adds proper validation to prevent the out-of-bounds write condition in the flashc component. Since this is a local privilege escalation requiring System privileges, ensure patch deployment follows standard change management procedures.

Fix this in Yocto Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
21.0 hours of engineering $3,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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