dbcve.org
Rdk BApplication · Rdkcentral

CVE-2024-20136

MEDIUM · 6.2 CVSS v3.1 Published 2024-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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 da, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS09121847; Issue ID: MSV-1821.

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 missing bounds check in the 'da' (daemon) component allows an out-of-bounds read, enabling local information disclosure without requiring elevated privileges or user interaction.

MitigationApply patch ALPS09121847 to implement proper bounds checking in the affected daemon 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= 2024q1
AndroidOperating system
Affected:= 12.0= 13.0= 14.0= 15.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 your device firmware and version
    Determine the exact firmware version of your RDK-based device, Android set-top box, or OpenWrt router. For RDK devices, check the firmware build string or version file. For Android devices, check Settings > About Phone/Tablet > Android version. For OpenWrt, check /etc/openwrt_version or run 'cat /etc/os-release'.
    Affected if The firmware version matches 2022q3 or 2024q1 for RDK, Android versions 12.0, 13.0, 14.0, or 15.0, or OpenWrt versions 19.07.0, 21.02.0, or 23.05.
  2. Locate the daemon component
    Identify if a daemon process named 'da' or associated with the 'da' component is running on your device. Check running processes using 'ps' command or examine the process list via /proc filesystem. Look for daemon processes that may handle the vulnerable bounds check area.
    Affected if A process corresponding to the 'da' daemon component is present and running on the system.
  3. Verify the daemon is accessible
    Confirm the daemon component is actively listening or accessible on the device. Check for open ports or socket files associated with the daemon. Use commands like 'netstat' or 'ss' to identify listening services.
    Affected if The daemon component is running and accessible without requiring elevated privileges, making it exploitable for local information disclosure.

Your environment is affected if you are running one of the specified product versions AND the vulnerable 'da' daemon component is present and accessible on your device.

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 patch ALPS09121847 to implement proper bounds checking in the affected daemon component.

Recommended fix Moderate confidence

Contact MediaTek or your device OEM for the specific fixed firmware version; the patch ID ALPS09121847 corresponds to the fix for issue MSV-1821

  1. Contact MediaTek technical support to obtain the patch with ID ALPS09121847
  2. Contact your device manufacturer (OEM) for the specific firmware update containing this security fix
  3. Apply the vendor-supplied firmware update to your device once available
  4. Verify the patch has been applied by checking system logs or using vulnerability scanning tools

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

Fix this in Rdk B Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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