dbcve.org
YoctoApplication · Linuxfoundation

CVE-2024-20080

CRITICAL · 9.8 CVSS v3.1 Published 2024-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 gnss service, there is a possible escalation of privilege due to improper certificate validation. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08720039; Issue ID: MSV-1424.

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 remote code execution vulnerability exists in the gnss service due to improper certificate validation. The lack of proper certificate validation allows an attacker to perform a man-in-the-middle attack, potentially intercepting and modifying communications to the gnss service and achieving remote privilege escalation without requiring any user interaction or additional privileges.

MitigationApply patch ALPS08720039 which implements proper certificate validation in the gnss service. Until the patch is available, restrict network access to trusted networks and monitor for unusual gnss service activity.

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= 4.0
Rdk BApplication
Affected:= 2022q3
AndroidOperating system
Affected:= 13.0= 14.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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 platform and version
    Determine the operating system or platform running on the device (Linuxfoundation Yocto, Rdkcentral Rdk B, or Google Android). For Yocto, check /etc/issue or use 'cat /etc/os-release'. For Android, go to Settings > About Phone. For Rdk B, check the firmware version information.
    Affected if The platform matches one of the affected products (Yocto 2.6, 3.3, or 4.0; Rdk B 2022q3; Android 13.0 or 14.0)
  2. Verify gnss service is present
    Check if the gnss service is installed and running on the system. On Linux-based systems, run 'ps aux | grep gnss' or check for gnss-related processes. On Android, verify gnss-related system services are active.
    Affected if The gnss service is present and running on the device
  3. Confirm gnss service network exposure
    Determine if the gnss service is accessible over the network. Check listening ports and network configuration using commands like 'netstat -tulpn | grep gnss' or review firewall rules. The vulnerability allows MITM attacks, so network accessibility is relevant.
    Affected if The gnss service is network-accessible from untrusted networks
  4. Compare installed version against affected ranges
    For Yocto: check the Yocto version using 'cat /etc/version' or the build system metadata. For Android: check the Android version in Settings > About Phone > Android version. For Rdk B: check the RDK-B firmware version.
    Affected if The installed version exactly matches 2.6, 3.3, or 4.0 for Yocto; 2022q3 for Rdk B; or 13.0 or 14.0 for Android

The environment is affected if the device runs one of the specific affected versions (Yocto 2.6/3.3/4.0, Rdk B 2022q3, or Android 13.0/14.0) and has the gnss service enabled and network-accessible.

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 patch ALPS08720039 which implements proper certificate validation in the gnss service. Until the patch is available, restrict network access to trusted networks and monitor for unusual gnss service activity.

Recommended fix Moderate confidence

Contact MediaTek for the patched ALPS release containing MSV-1424 fix; OEMs must integrate patch ALPS08720039 into their device-specific updates

  1. Contact MediaTek to obtain patch ALPS08720039 containing the certificate validation fix
  2. Apply the MediaTek ALPS08720039 patch to the gnss service component
  3. For Yocto-based systems: Rebuild the system image with the patched MediaTek components after obtaining the fix from your MediaTek chipset provider
  4. For Android devices: Wait for and apply the OEM/system update that incorporates the MediaTek patch (ALPS08720039)
  5. Verify that the gnuss service properly validates certificates after patching
Caveat OEMs should test certificate validation behavior after applying the MediaTek gnss patch to ensure compatibility with location services

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

Fix this in Yocto Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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