dbcve.org
AndroidOperating system · Google

CVE-2024-20110

MEDIUM · 6.7 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 →
69/100
Remediation priority · Elevated
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 ccu, there is a possible out of bounds write 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: ALPS09065887; Issue ID: MSV-1762.

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 ccu component allows an out-of-bounds write, enabling local privilege escalation from System execution privileges. The vulnerability requires System-level access to exploit but needs no user interaction.

MitigationApply vendor patch ALPS09065887 to address the missing bounds check in the ccu component and prevent the out-of-bounds write condition.

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
AndroidOperating system
Affected:= 12.0= 13.0= 14.0= 15.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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/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. Check Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The version is 12.0, 13.0, 14.0, or 15.0 exactly (note: this affects only these specific versions, not range)
  2. Identify CCU component presence
    Examine system logs or /system components for ccu module; check vendor-specific configurations via 'ls -la /vendor/lib/modules/' or similar vendor module directories
    Affected if The CCU component is present and loaded on the device
  3. Verify System-level access context
    Confirm the application or process runs with System-level Android permissions (UID 1000) rather than root or user-level
    Affected if Exploiting requires System-level access - verify if any third-party apps or services have System permissions that could be leveraged
  4. Check for patch ALPS09065887
    Query the system build fingerprint or security patch level via 'getprop ro.build.version.security_patch' or 'getprop ro.vendor.build.security_patch'
    Affected if The patch is NOT applied - the security patch level is dated before the vendor fix was released

The environment is affected if the device runs Android 12.0, 13.0, 14.0, or 15.0 exactly, contains the CCU component, and does not have patch ALPS09065887 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patch ALPS09065887 to address the missing bounds check in the ccu component and prevent the out-of-bounds write condition.

Recommended fix Moderate confidence

Android 12.0, 13.0, 14.0, or 15.0 with January 2024 or later Android Security Patch Level

  1. Check for and install the latest Android system updates for your device, as MediaTek security patches are typically delivered through monthly Android Security Patch Level (SPL) updates
  2. Verify the Android Security Patch Level is at least January 2024 or later (the month when this vulnerability was addressed)
  3. If using a custom ROM or device without official updates, contact the device manufacturer (OEM) for a firmware update containing MediaTek patch ALPS09065887
  4. For enterprise/managed devices, push the system update through your mobile device management (MDM) console
Caveat Ensure device compatibility before applying system updates; some OEM customizations may have compatibility constraints

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

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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