dbcve.org
AndroidOperating system · Google

CVE-2024-20013

MEDIUM · 6.7 CVSS v3.1 Published 2024-02-05
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 keyInstall, 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: ALPS08471742; Issue ID: ALPS08308608.

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 · high confidence

A missing bounds check in the keyInstall component allows an out-of-bounds write, enabling a local attacker with System-level execution privileges to escalate to higher privileges. The vulnerability involves memory corruption through improper array or buffer indexing.

MitigationApply vendor patch ALPS08471742 which adds the missing bounds check to prevent the out-of-bounds write in keyInstall. This is a low-level system component fix requiring system-level privileges to apply.

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:= 11.0= 12.0= 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
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
    Run 'getprop ro.build.version.release' or check Settings > About Phone > Android version
    Affected if Version is 11.0, 12.0, 13.0, or 14.0 exactly as listed in affected versions
  2. Verify security patch level
    Run 'getprop ro.build.version.security_patch' to see the installed security patch date
    Affected if Security patch level is earlier than the vendor patch release date for ALPS08471742, or patch level cannot be verified
  3. Check keyInstall component presence
    Review system logs (logcat) or system partition files for keyInstall module usage; run 'dumpsys' on keymaster or keystore services
    Affected if keyInstall component is present and actively handling key operations on the device
  4. Confirm system-level execution context
    Identify if any application or service on the device runs with System-level privileges (check process list via 'ps -A' or 'dumpsys activity processes')
    Affected if Any process with UID system or root privileges exists on the device, as the attacker needs System-level access to exploit this flaw
  5. Check for patch application status
    Query build fingerprint or vendor-specific props: 'getprop ro.build.fingerprint' and compare against known patched build identifiers, or check 'getprop' for ALPS08471742 references
    Affected if The patch ALPS08471742 is not reflected in the system build properties or security patch metadata

The environment is affected if the device runs Android 11.0, 12.0, 13.0, or 14.0 exactly, contains the keyInstall component, has System-level processes present, and lacks verification that patch ALPS08471742 has 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.

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

Apply vendor patch ALPS08471742 which adds the missing bounds check to prevent the out-of-bounds write in keyInstall. This is a low-level system component fix requiring system-level privileges to apply.

Recommended fix Moderate confidence
  1. Check if the device uses a MediaTek chipset by reviewing the device specifications or using system information apps
  2. Contact the device manufacturer (OEM) to confirm if the ALPS08471742 patch has been applied to your device's firmware
  3. For enterprise/IT-managed devices, check with your mobile device management (MDM) provider for available security patch updates that include the MediaTek fix
  4. If the device manufacturer has released a security update containing the MediaTek ALPS08471742 patch, apply it as soon as possible
  5. Verify the patch has been applied by checking the Android security patch level in Settings > About Phone > Security Patch Level

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

Fix this in Android 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-20013 — 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-20013 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