CVE-2024-20090
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 vdec, 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: ALPS09028313; Issue ID: MSV-1703.
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 vdec (video decoder) component allows an out of bounds write, which can be exploited for local privilege escalation to System execution level without requiring 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.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 12.0Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The version listed is exactly 12.0 (not 12.0.x, 13, 14, etc.)
-
Confirm vdec component is presentCheck for vdec device node by running 'ls -la /dev/vdec*' or 'cat /proc/devices | grep vdec' in ADB shellAffected if The vdec device node or driver exists on the device
-
Verify System privilege access existsRun 'id' or 'whoami' via ADB shell to check current user context; check if app can attain System-level privileges through local exploitsAffected if The device allows local applications to escalate privileges to the System user context
-
Check for vulnerable vdec ioctl callsAnalyze vdec kernel driver for missing bounds checks in ioctl handlers, or check vendor security bulletins for vdec vulnerability detailsAffected if The vdec driver handles video decoding without proper boundary validation on input parameters
-
Confirm MediaTek chipset usageRun 'getprop ro.hardware' or check /proc/cpuinfo to identify the SoC vendor; vdec is typically a MediaTek componentAffected if The device uses a MediaTek chipset running Android 12.0
A device is affected if it runs Android version 12.0 exactly, contains the vdec video decoder component, and allows local privilege escalation to System level through the vulnerable bounds check in vdec.
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.
From vendor dataApply vendor patch ALPS09028313 to add proper bounds validation in the vdec component. Prioritize patching on devices with vdec functionality exposed to local attackers.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20090 — 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-20090 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