CVE-2022-20075
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 ged, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS05838808; Issue ID: ALPS05838808.
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 · high confidenceIn ged (a graphical editor component in Mediatek/Alpine devices), an integer overflow vulnerability exists that can lead to an out-of-bounds write. This allows a local attacker to escalate privileges to System level 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= 10.0= 11.0= 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.
-
Check Android versionGo to Settings > About Phone > Android version or run 'getprop ro.build.version.release'Affected if Android version is 10.0, 11.0, or 12.0 (exact match)
-
Identify chipset vendorRun 'getprop ro.chipname' or check /proc/cpuinfo for Mediatek/Alpine identifiersAffected if Device uses Mediatek or Alpine chipset (ged is specific to these platforms)
-
Confirm ged component presenceCheck for /system/bin/ged or /vendor/bin/ged binary, or run 'ls -la /system/bin/ged' if it existsAffected if ged binary exists on the device - the vulnerability only applies if this component is present
-
Check ged version or patch levelRun 'getprop ro.build.version.security_patch' to see applied security patches, or check ged binary version if accessibleAffected if Security patch level is earlier than the vendor fix ALPS05838808, or patch level is unknown/unapplied
Device is affected if running Android 10/11/12 on a Mediatek/Alpine chipset with the ged component present and without the ALPS05838808 patch applied.
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 ALPS05838808 which addresses the integer overflow in ged to prevent out-of-bounds writes and privilege escalation.
Android Security Patch Level May 2022 or later (which includes MediaTek patch ALPS05838808)
- 1. Check your Android device's current Security Patch Level in Settings > About Phone > Software Information > Security Patch Level
- 2. Verify the device has received the Android Security Bulletin patch that includes CVE-2022-20075
- 3. If the device has not been updated, check for system updates in Settings > System > System Update
- 4. If no update is available, contact the device manufacturer (OEM) for the specific patch ALPS05838808
- 5. For enterprise/IT-managed devices, ensure Mobile Device Management (MDM) policies are updated to require minimum Security Patch Level of May 2022 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20075 — 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-2022-20075 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