CVE-2024-20059
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 · uneditedIn da, there is a possible escalation of privilege due to an incorrect status check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS08541749; Issue ID: ALPS08541749.
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 confidenceA local privilege escalation vulnerability exists in a system daemon (da) due to an incorrect status check. The flaw allows a local attacker with System execution privileges to escalate privileges without user interaction.
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= 12.0= 13.0= 14.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Android version is affectedCheck device settings under About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The installed Android version is 12.0, 13.0, or 14.0 exactly
-
Confirm system daemon component is presentList running system daemons using 'ps -A | grep -E "daemon|system"' or check /system/bin/ for daemon binaries. The vulnerability exists in a system daemon identified as 'da' in the component notation.Affected if A system daemon binary matching the vulnerable component exists on the device
-
Check process privilegesRun 'ps -A | grep [daemon_name]' to identify the running daemon process, then check its SELinux context with 'ls -laZ /proc/[pid]' if availableAffected if The daemon runs with elevated System-level privileges, which is required for the privilege escalation to be exploitable
-
Identify System-level users presentCheck for accounts with System execution level using 'dumpsys activity users' or reviewing installed apps with System privileges via 'dumpsys package'Affected if There are users or applications holding System execution privileges on the device, which would satisfy the attacker's initial access requirement
The device is affected if it runs Android 12.0, 13.0, or 14.0 and contains the vulnerable system daemon component, allowing a local attacker with System-level access to escalate privileges.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply patch ALPS08541749 to address the incorrect status check in the affected daemon component.
- Check with your device manufacturer (OEM) if they have released a security update that includes MediaTek patch ID ALPS08541749
- If your device manufacturer has released an update containing this patch, apply the latest available security update for your Android device
- If no update is available from your manufacturer, monitor for future security releases that include this patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-20059 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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