dbcve.org
YoctoApplication · Linuxfoundation

CVE-2024-20054

MEDIUM · 6.6 CVSS v3.1 Published 2024-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable 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 gnss, there is a possible escalation of privilege due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08580200; Issue ID: ALPS08580200.

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

This is a local privilege escalation vulnerability in the GNSS (Global Navigation Satellite System) component. The vulnerability is caused by a missing bounds check, which could allow a local attacker to escalate privileges to System level. No user interaction is required for exploitation.

MitigationApply patch ALPS08580200 which adds proper bounds checking to the GNSS component to prevent the privilege escalation. This is a vendor-supplied patch that should be applied through the device OEM's firmware update process.

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:= 2.6= 3.3
Rdk BApplication
Affected:= 2022q3
AndroidOperating system
Affected:= 13.0= 14.0
OpenwrtOperating system
Affected:= 19.07.0= 21.02.0

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
Network
Complexity
High
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/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 if GNSS component is present
    Check for GNSS-related processes, services, or hardware: look for 'gnss', 'location', 'gps' in running processes (ps aux), or check for gnss device nodes in /dev (e.g., /dev/gnss*). On Android, check for location services or GPS HAL.
    Affected if GNSS component is present and running on the device
  2. Determine the base OS or firmware version
    On Yocto: check /etc/version or cat /etc/os-release. On RDK B: check the firmware version via 'cat /version' or similar. On Android: Settings > About Phone > Build Number. On OpenWRT: check /etc/openwrt_version or 'cat /etc/os-release'.
    Affected if The version matches exactly 2.6 or 3.3 for Yocto, 2022q3 for RDK B, 13.0 or 14.0 for Android, or 19.07.0 or 21.02.0 for OpenWRT
  3. Check for patch applied to GNSS component
    If accessible, examine the GNSS library or binary (typically found in /usr/lib or /vendor/lib) and look for the patch level or check vendor documentation for the presence of ALPS08580200. On Android, check the security patch level in Settings > Security > Security patch level.
    Affected if The system lacks the ALPS08580200 patch or shows a security patch level prior to the fix being applied
  4. Verify if the device allows local shell access
    Confirm whether local unprivileged access is possible (e.g., ADB shell, telnet, SSH to a low-privileged user). This is required for the local privilege escalation to be exploitable.
    Affected if Local unprivileged access exists and the GNSS component is present on a vulnerable version

A user is affected if the GNSS component is present on a system running any of the exact affected versions (Yocto 2.6/3.3, RDK B 2022q3, Android 13.0/14.0, OpenWRT 19.07.0/21.02.0) and the ALPS08580200 patch has not been applied.

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 patch ALPS08580200 which adds proper bounds checking to the GNSS component to prevent the privilege escalation. This is a vendor-supplied patch that should be applied through the device OEM's firmware update process.

Fix this in Yocto Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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