dbcve.org
Rdk BApplication · Rdkcentral

CVE-2024-20006

MEDIUM · 6.7 CVSS v3.1 Published 2024-02-05
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 da, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08477148; Issue ID: ALPS08477148.

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

Out of bounds write vulnerability in a system daemon (identified by ALPS) due to a missing bounds check. The flaw allows local privilege escalation to System execution level without requiring user interaction.

MitigationApply vendor patch ALPS08477148 which adds proper bounds validation to prevent the out of bounds write condition in the affected daemon.

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:= 11.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 device firmware or OS type
    Determine if the system is running RDKB (Rdkcentral), Google Android, or OpenWrt. This can be done via /etc/os-release, uname -a, or checking system information menus.
    Affected if The system is running one of the listed platforms (RDKB, Android 11.0, or OpenWrt 19.07.0/21.02.0)
  2. Check installed firmware or OS version
    Run 'version' or 'cat /etc/os-release' to obtain the exact installed version. For RDKB devices, check the firmware version via web UI or SNMP. For Android, check Settings > About Phone > Android version. For OpenWrt, run 'cat /etc/openwrt_version' or check /etc/banner.
    Affected if The installed version matches exactly 2022q3 for RDKB, 11.0 for Android, 19.07.0 for OpenWrt, or 21.02.0 for OpenWrt
  3. Locate the ALPS system daemon
    Search for processes or services labeled as ALPS or system daemons that handle the identified vulnerable component. Check running processes via 'ps' or 'top' and look for ALPS-related services. Review init scripts or systemd services.
    Affected if An ALPS system daemon is present and running on the device with the affected OS version
  4. Verify daemon executes with elevated privileges
    Check the process ownership and permissions of the ALPS daemon using 'ps aux | grep [daemon_name]' and 'ls -la /path/to/daemon' or equivalent. Determine if it runs as root or a privileged user.
    Affected if The ALPS daemon runs with root or system-level privileges, which is required for the privilege escalation to be exploitable
  5. Confirm the daemon is accessible from the attack surface
    Verify the daemon is exposed via a local service, socket, or interface that a local attacker could interact with. Check for exposed ports, Unix sockets, or IPC mechanisms via 'netstat -tulpn' or reviewing service configurations.
    Affected if The daemon is accessible locally without authentication barriers, allowing a local user to trigger the vulnerable code path

A system is affected if it runs exactly version 2022q3 (RDKB), 11.0 (Android), 19.07.0, or 21.02.0 (OpenWrt) AND contains the vulnerable ALPS system daemon running with elevated 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch ALPS08477148 which adds proper bounds validation to prevent the out of bounds write condition in the affected daemon.

Recommended fix Moderate confidence

MediaTek ALPS release containing patch ALPS08477148 (any release newer than 2022q3 for RDK B; Android 12+ for Android; newer OpenWRT with patched MediaTek components)

  1. 1. Identify the MediaTek chipset/model in the affected device
  2. 2. Obtain the MediaTek ALPS firmware update that includes patch ALPS08477148
  3. 3. For RDK B devices: Update to a release newer than 2022q3 that incorporates the MediaTek security patch
  4. 4. For Android devices: Update to Android 12 or later, or apply the monthly security patch that includes ALPS08477148
  5. 5. For OpenWRT devices: Update to a newer OpenWRT release that includes the patched MediaTek firmware components
  6. 6. Verify the update was applied by checking the device firmware version
Caveat Firmware updates may require device downtime and could have compatibility implications with custom configurations

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

Fix this in Rdk B Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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