dbcve.org
YoctoApplication · Linuxfoundation

CVE-2024-20053

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

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 local privilege escalation vulnerability exists in the flashc component where an uncaught exception leads to an out-of-bounds write. An attacker with System execution privileges can exploit this to escalate to higher privileges. No user interaction is required.

MitigationApply the vendor patch ALPS08541757 which addresses proper exception handling and bounds checking in the flashc component. This typically requires a firmware or software update from the device vendor.

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

CVSS:3.1/AV:L/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 flashc component presence
    Check if the flashc component is present on the system. This may be a binary, library, or service. Look for files or processes named 'flashc' or related storage/flash management components.
    Affected if The flashc component is present and running on the device.
  2. Determine the product version
    Identify the installed version of the affected product (Yocto 3.3, RDK B 2022q3, Android 12.0/13.0/14.0, or OpenWRT 19.07.0/21.02.0) using system information commands such as 'cat /etc/version', 'getprop ro.build.version.release' on Android, or 'opkg list-installed' on OpenWRT.
    Affected if The installed version matches one of the affected versions listed in the CVE (Yocto 3.3, RDK B 2022q3, Android 12.0/13.0/14.0, or OpenWRT 19.07.0/21.02.0).
  3. Verify current execution privileges
    Check the current user's privilege level using commands like 'id', 'whoami', or checking if the process runs with System/Android system privileges. For embedded devices, check if the running process or service has elevated execution context.
    Affected if The current execution context has System-level privileges, creating the preconditions for exploitation.
  4. Check for the vulnerability-specific behavior
    Since this is an uncaught exception leading to out-of-bounds write in flashc, monitor for unexpected crashes, memory corruption indicators, or privilege escalation attempts originating from flashc-related processes. Review system logs for flashc-related error messages or stack traces.
    Affected if Evidence of unhandled exceptions or memory corruption involving the flashc component is observed.

A system is affected if it runs any of the listed product versions (Yocto 3.3, RDK B 2022q3, Android 12.0/13.0/14.0, or OpenWRT 19.07.0/21.02.0) with the flashc component present and the attacker has System-level execution privileges.

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 ALPS08541757 which addresses proper exception handling and bounds checking in the flashc component. This typically requires a firmware or software update from the device vendor.

Fix this in Yocto Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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