dbcve.org
YoctoApplication · Linuxfoundation

CVE-2024-20104

HIGH · 8.4 CVSS v3.1 Published 2024-11-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
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 write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: ALPS09073261; Issue ID: MSV-1772.

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 daemon component due to missing bounds check, allowing local privilege escalation. Exploitation requires user interaction but no additional execution privileges.

MitigationApply vendor patch ALPS09073261 to implement proper bounds validation 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
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
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/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 your build environment and version
    Determine which affected product (Yocto, RDK-B, Android, or OpenWrt) is in use and check its specific version string (e.g., run 'cat /etc/os-release' on Linux-based systems or check system settings on Android)
    Affected if The installed product matches any version listed in the affected ranges (Yocto 4.0, RDK-B 2022q3 or 2024q1, Android 12.0-15.0, or OpenWrt 19.07.0, 21.02.0, 23.05)
  2. Locate the 'da' component
    Search for a daemon or service named 'da' or containing 'da' in its name on the system (check /etc/init.d/, /system/bin/, /usr/sbin/, or service listings depending on platform)
    Affected if The 'da' component is present on the system
  3. Check if the daemon is running
    Run 'ps aux' or platform-specific process listing command to see if the daemon is actively running
    Affected if The daemon is actively executing on the system
  4. Determine daemon version
    Query the daemon version using 'da --version', 'da -v', or check the binary directly if version flags are unavailable
    Affected if The daemon version cannot be determined or matches the vulnerable release versions

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 ALPS09073261 to implement proper bounds validation in the affected daemon component.

Fix this in Yocto Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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