dbcve.org
YoctoApplication · Linuxfoundation

CVE-2024-20107

MEDIUM · 6.2 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 →
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: ALPS09124360; Issue ID: MSV-1823.

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' component allows an out of bounds read operation, enabling local information disclosure without requiring elevated privileges or user interaction. The vulnerability stems from inadequate input validation that fails to verify buffer boundaries before reading data.

MitigationApply the provided patch ALPS09124360 to address the missing bounds check in the affected daemon component. Since this is a local information disclosure issue with no user interaction required, prioritize patching affected systems to prevent potential data exposure.

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
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 OS distribution and version
    Run 'cat /etc/os-release' on Linux-based systems, or check system settings on Android. For embedded systems like Yocto, RDK, or OpenWrt, check '/etc/version', '/etc/os-release', or the firmware version information.
    Affected if The distribution matches Linuxfoundation Yocto 4.0, Rdkcentral Rdk B 2022q3 or 2024q1, Google Android 12.0, 13.0, 14.0, or 15.0, or Openwrt 19.07.0, 21.02.0, or 23.05.
  2. Confirm the affected daemon component is present
    Identify the specific 'da' daemon component in your environment. Since the CVE references a 'da' component (daemon), check running processes for any daemon with 'da' in the name or purpose related to the vulnerable service. Use 'ps aux' or check system service listings.
    Affected if The 'da' daemon component is installed and running on the affected system.
  3. Check if the daemon is enabled
    Verify the daemon service is active by checking system services. On systemd systems, run 'systemctl list-units --type=service | grep -i da' or check service status. On OpenWrt, check '/etc/init.d/' for the service and its status.
    Affected if The daemon is actively running as a service on the system.
  4. Review system logs for anomalous read operations
    Check system and application logs for any warnings related to buffer reads, memory access errors, or information disclosure. Look for patterns like 'out of bounds', 'buffer overflow', or 'invalid read' in journalctl, dmesg, or application-specific logs.
    Affected if Logs show out-of-bounds read errors or unexpected memory access patterns from the daemon component.

You are affected if your system runs one of the specifically listed versions (Yocto 4.0, RDK B 2022q3/2024q1, Android 12-15, or OpenWrt 19.07.0/21.02.0/23.05) AND the vulnerable 'da' daemon component is installed and running.

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 the provided patch ALPS09124360 to address the missing bounds check in the affected daemon component. Since this is a local information disclosure issue with no user interaction required, prioritize patching affected systems to prevent potential data exposure.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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