dbcve.org
AndroidOperating system · Google

CVE-2024-20028

MEDIUM · 6.6 CVSS v3.1 Published 2024-03-04
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 da, there is a possible out of bounds write due to lack of valudation. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08541632; Issue ID: ALPS08541687.

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

An out-of-bounds write vulnerability in a daemon component due to lack of input validation allows a local attacker with System-level execution privileges to escalate to full privilege escalation. No user interaction is required for exploitation.

MitigationApply vendor patch ALPS08541632 to the affected daemon/driver component. Verify no regression in service functionality post-patch.

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

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. Check Android version
    Run 'getprop ro.build.version.release' or check Settings > About Phone to determine the Android OS version
    Affected if Version is exactly 12.0, 13.0, or 14.0
  2. Verify patch ALPS08541632 is applied
    Check system build fingerprint or patch level via 'getprop ro.build.version.security_patch' and compare against vendor patch release notes for ALPS08541632
    Affected if Patch level is earlier than the vendor release containing ALPS08541632 or patch is not present
  3. Identify vulnerable daemon component
    Review process list via 'ps -A' for the specific daemon/driver named in the vendor advisory for this CVE; cross-reference with /system/vendor or /vendor partition daemons
    Affected if The daemon component referenced in the CVE advisory is running on an unpatched system version
  4. Confirm System-level execution context
    Determine if the daemon runs with elevated privileges by checking its process attributes via 'ps -Z <daemon_name>' or examining its SELinux context
    Affected if The daemon executes with System or root privileges and the system version matches affected Android versions without the patch applied

A user is affected if their Android device runs version 12.0, 13.0, or 14.0 and the patch ALPS08541632 has not been applied to the vulnerable daemon component.

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 ALPS08541632 to the affected daemon/driver component. Verify no regression in service functionality post-patch.

Recommended fix Moderate confidence
  1. 1. Check the current Android security patch level on the affected device by going to Settings > About Phone > Security Patch Level
  2. 2. Verify if the device has received the Android Security Bulletin patch that addresses CVE-2024-20028. This vulnerability is associated with MediaTek patch ID ALPS08541632
  3. 3. Contact the device OEM (Original Equipment Manufacturer) to confirm if a patch is available for your specific device model
  4. 4. Apply the latest available Android security update for the device, which should include the fix for this MediaTek vulnerability
  5. 5. If no update is available from the OEM, monitor for future monthly security patch releases that include the MediaTek fix

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

Fix this in Android Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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