dbcve.org
YoctoApplication · Linuxfoundation

CVE-2024-20144

MEDIUM · 6.6 CVSS v3.1 Published 2025-01-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
No privileges

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 V6 DA, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege, if an attacker has physical access to the device, with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: ALPS09167056; Issue ID: MSV-2041.

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 V6 DA leads to an out-of-bounds write vulnerability, allowing local privilege escalation. Exploitation requires physical access to the device and user interaction, with no additional execution privileges needed.

MitigationApply the vendor security patch (ALPS09167056) to affected devices. Since physical access is required for exploitation, ensure devices are not left unattended in accessible locations.

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:= 4.0
Rdk BApplication
Affected:= 2022q3= 2024q1
AndroidOperating system
Affected:= 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
Physical
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:R/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 operating system product and version
    Run 'cat /etc/os-release' or 'uname -a' to determine the installed OS product and version
    Affected if The product matches Yocto 4.0, RDK B 2022q3 or 2024q1, Android 13.0/14.0/15.0, or OpenWRT 19.07.0/21.02.0/23.05
  2. Confirm Android version for Android-based devices
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if The Android version is exactly 13.0, 14.0, or 15.0
  3. Confirm OpenWRT version for OpenWRT devices
    Run 'cat /etc/openwrt_release' or 'opkg list-installed' to identify the OpenWRT release version
    Affected if The OpenWRT release is exactly 19.07.0, 21.02.0, or 23.05
  4. Check for presence of V6 DA component
    Search for V6 DA related kernel modules or drivers: 'lsmod | grep -i v6' or 'find /lib/modules -name "*v6*"'
    Affected if A V6 DA driver or kernel module is loaded and the system version matches an affected release
  5. Detect potential privilege escalation indicators
    Review system logs for unexpected privilege escalation events: 'journalctl -b | grep -i error' or 'dmesg | grep -i denied'
    Affected if Unusual privilege escalation events are found on a system matching affected versions

The system is likely affected if it runs one of the specific version releases (Yocto 4.0, RDK B 2022q3/2024q1, Android 13.0/14.0/15.0, or OpenWRT 19.07.0/21.02.0/23.05) and the V6 DA component is present, with physical access being a key requirement for exploitation.

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 the vendor security patch (ALPS09167056) to affected devices. Since physical access is required for exploitation, ensure devices are not left unattended in accessible locations.

Recommended fix Moderate confidence

Apply security updates containing MediaTek patch ALPS09167056 (Android devices: January 2024 security patch level or later; other platforms: vendor-specific update)

  1. 1. Identify the MediaTek chipset/device model affected by checking system information or device documentation
  2. 2. Check if your device manufacturer has released a security update that includes the ALPS09167056 patch (CVE-2024-20144)
  3. 3. For Android devices: Go to Settings > Security > Security update level and verify the patch level is January 2024 or later
  4. 4. For Yocto/RDKB/OpenWRT devices: Check with your device vendor or distribution maintainer for MediaTek firmware updates incorporating the ALPS09167056 patch
  5. 5. Apply the available security update from your device manufacturer or distribution
  6. 6. Verify the patch has been applied by checking the security patch date in system settings
  7. 7. As a secondary mitigation: Restrict physical access to the device and avoid connecting untrusted peripherals
Caveat Security updates are generally backward compatible; ensure backup of critical data before applying updates

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

Fix this in Yocto Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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