dbcve.org
Rdk BApplication · Rdkcentral

CVE-2024-20056

MEDIUM · 6.7 CVSS v3.1 Published 2024-05-06
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 preloader, there is a possible escalation of privilege due to an insecure default value. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08528185; Issue ID: ALPS08528185.

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 preloader component due to an insecure default value. An attacker with System execution privileges can exploit this to elevate to higher privileges without user interaction.

MitigationApply vendor patch ALPS08528185 to address the insecure default value in the preloader component.

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
Rdk BApplication
Affected:= 2022q3
AndroidOperating system
Affected:= 12.0= 13.0= 14.0
OpenwrtOperating system
Affected:= 19.07.0= 21.02.0= 23.05

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 product and version
    Determine the exact firmware/software version of the device or system. For Android, check Settings > About Phone > Build Number. For OpenWRT, check /etc/openwrt_version or use 'cat /etc/os-release'. For RDK, check the firmware version via the device admin interface or kernel log.
    Affected if The installed version matches Android 12.0, 13.0, or 14.0; OpenWRT 19.07.0, 21.02.0, or 23.05; or RDKcentral RDK B 2022q3
  2. Verify preloader component presence
    Check if the preloader component is present on the system. On Android, examine boot partition files in /boot or /system/vendor. On OpenWRT, check /lib/preinit or bootloader configuration files. On RDK devices, examine the early boot components.
    Affected if The preloader component is installed and active in the early boot process
  3. Confirm System execution privileges available
    Verify that the account or context from which you are checking has System-level execution privileges. On Android, this typically requires ADB shell with root access or a root shell. On OpenWRT, check if you have root access via SSH or serial console. On RDK, verify root or System-level access.
    Affected if System or root-level execution context is accessible on the device
  4. Inspect preloader configuration for insecure defaults
    Examine the preloader configuration files or boot parameters for default values that could allow privilege escalation. Look for configuration files in /boot, /system/vendor/boot, or early boot scripts. Check for permissive settings, unsigned code execution options, or debug flags enabled by default.
    Affected if The preloader configuration contains insecure default values such as permissive permissions, disabled signature verification, or debug modes enabled by default

A user is affected if they are running one of the specific affected versions AND the preloader component with an insecure default configuration is present and they have System execution privileges available for an attacker to leverage.

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 vendor patch ALPS08528185 to address the insecure default value in the preloader component.

Fix this in Rdk B Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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