dbcve.org
YoctoApplication · Linuxfoundation

CVE-2024-20143

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-2069.

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

In V6 DA (Device Analyzer), a missing bounds check allows an out-of-bounds write vulnerability. This could enable a locally authenticated attacker with physical device access to escalate privileges by writing beyond allocated memory boundaries, requiring user interaction to trigger.

MitigationApply vendor patch ALPS09167056 to address the missing bounds check in V6 DA; ensure physical security controls are maintained as the attack requires physical device access.

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:= 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
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 if V6 Device Analyzer is present
    Search for the Device Analyzer component or daemon on the system. Common locations may include /system/bin/, /vendor/bin/, or check running processes for 'da', 'device_analyzer', or similar processes. Use 'ps -A | grep -i da' or check /proc/<pid>/cmdline for related processes.
    Affected if The V6 Device Analyzer component is found running on the system
  2. Determine the Device Analyzer version
    Retrieve the version of the installed Device Analyzer. This may be available via 'da --version', 'device_analyzer -v', checking the APK/system image metadata, or examining the binary/library version string in the compiled binary.
    Affected if The installed version matches one of: Yocto 4.0, RDK B 2022q3, RDK B 2024q1, Android 12.0/13.0/14.0/15.0, OpenWRT 19.07.0/21.02.0/23.05
  3. Verify physical access exposure
    Assess whether the device is physically accessible to unauthorized users. Check physical security controls, device location, tamper-evident seals, and whether the device is in a secured location versus a public area.
    Affected if The device can be accessed physically by untrusted individuals, enabling the local authentication attack vector
  4. Check for user interaction trigger mechanisms
    Examine if the device has user-facing interfaces (touchscreen, buttons, USB ports, debug interfaces) that could be leveraged to trigger the vulnerable code path in Device Analyzer.
    Affected if User interaction vectors exist that could trigger the out-of-bounds write condition

If the V6 Device Analyzer component is present and its version matches any of the affected versions (Yocto 4.0, RDK B 2022q3/2024q1, Android 12-15, OpenWRT 19.07/21.02/23.05), and the device has physical access exposure, the environment is likely affected by CVE-2024-20143.

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 ALPS09167056 to address the missing bounds check in V6 DA; ensure physical security controls are maintained as the attack requires physical device access.

Fix this in Yocto Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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