CVE-2023-20805
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 imgsys, 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: ALPS07199773; Issue ID: ALPS07326411.
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 imgsys (graphics system) component allows an out-of-bounds write vulnerability. An attacker with System-level execution privileges can exploit this to escalate privileges locally. The vulnerability requires no 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= 4.0= 12.0= 13.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.
-
Identify the operating system and versionOn Android: go to Settings > About Phone > Android version. On Yocto: run 'cat /etc/os-release' or 'cat /version' to determine the Yocto version.Affected if The system is running Android 12.0, Android 13.0, or Linuxfoundation Yocto 4.0
-
Determine if the imgsys graphics subsystem is presentCheck for imgsys-related processes, kernel modules, or device nodes. On Android, examine /proc/modules or look for imgsys in /sys/module/. On Yocto, check for imgsys kernel modules via 'lsmod' or examine /dev/ for graphics-related device entries.Affected if The imgsys component is loaded or present on the system
-
Verify the graphics system configurationExamine the graphics subsystem configuration files or check the imgsys driver version if accessible. On Android, this may involve checking /vendor or /system/lib/modules for imgsys-related libraries or drivers.Affected if An imgsys driver or component is installed without the ALPS07199773 patch applied
The system is affected if it runs Android 12.0 or 13.0 or Yocto 4.0 AND has the imgsys graphics subsystem present, because the missing bounds check vulnerability exists in the imgsys component of these specific versions.
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 ALPS07199773 to address the missing bounds check in the imgsys component.
- Contact your device manufacturer or Yocto BSP vendor to request the security update containing MediaTek patch ALPS07199773
- For Android devices, ensure the device has the latest Android Security Patch Level (SPL) that includes the MediaTek ALPS07199773 fix
- For Yocto systems, check with the BSP vendor for a Yocto 4.0 image update that includes the patched MediaTek imgsys component
- Verify the patch is applied by checking the MediaTek security bulletin or contacting MediaTek directly for patch verification
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20805 — 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-2023-20805 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