CVE-2024-20108
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 atci, 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: ALPS09082988; Issue ID: MSV-1774.
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 missing bounds check in the atci component allows an out-of-bounds write, enabling local privilege escalation from System execution privileges. No user interaction is required for exploitation.
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.0= 15.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 within affected rangeRun 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if Version is 12.0, 13.0, 14.0, or 15.0 exactly
-
Confirm atci component is presentCheck for /vendor/etc/init/atci.rc or /system/etc/init/atci.rc init scripts, or look for 'atci' in 'ps -A' outputAffected if The atci service or component files exist on the device
-
Check if atci service is runningRun 'ps -A | grep atci' to list any running atci processesAffected if An atci daemon or service process is running with System user privileges
-
Determine if vendor patch ALPS09082988 is appliedCheck /vendor/etc/nvcfg/atci/version or query specific ATCI-related build properties via 'getprop | grep atci'Affected if The patch is not present or the atci module shows an unpatched version/build date
Device is affected if it runs Android 12.0-15.0, has the atci component present and running with System privileges, and is missing the ALPS09082988 bounds check patch.
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 vendor patch ALPS09082988 to add proper bounds validation before memory write operations in the atci module.
Firmware version containing MediaTek patch ALPS09082988 - contact device OEM for specific version numbers
- Contact your device OEM (Original Equipment Manufacturer) to obtain a firmware update that includes MediaTek patch ALPS09082988
- Verify with the OEM that the patch addresses CVE-2024-20108 in the atci component
- If using MediaTek-based devices, check MediaTek's corporate security advisories at corp.mediatek.com for the specific fixed firmware version
- Apply the OEM firmware update through the manufacturer's standard update mechanism
- After update, verify the patch is applied by checking system security patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20108 — 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-20108 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