CVE-2022-21759
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 power service, 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: ALPS06419106; Issue ID: ALPS06419077.
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 confidenceOut of bounds write vulnerability in the power service due to a missing bounds check. This allows local privilege escalation from System execution privileges, with no user interaction required.
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= 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 versionRun 'getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if Version equals 11.0 or 12.0 exactly (not a range, the specific versions listed)
-
Verify power service component existsCheck for 'power' service via 'adb shell dumpsys' or inspect /system/bin/ or /vendor/bin/ for power service binariesAffected if Power service component is present on the device (this is required for the vulnerability to exist)
-
Confirm process runs with System privilegesRun 'adb shell ps -A | grep power' and check UID (should show 'system' or UID 1000) or examine SELinux context via 'ls -Z' on the service binaryAffected if The power service process runs with System-level privileges (UID 1000 or 'system' user)
-
Verify vendor patch statusCheck system build fingerprint or vendor security patch level via 'getprop ro.build.version.security_patch' - vendor patch ALPS06419106 addresses issue ALPS06419077Affected if Vendor security patch level is earlier than the fix containing ALPS06419106, or patch status is unknown/unavailable
Device is affected if running Android 11.0 or 12.0 exactly, contains the power service component, and the vendor patch ALPS06419106 has not been 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 ALPS06419106 addressing issue ALPS06419077 to the affected power service component.
January 2022 Android Security Patch Level (SPL) or later; contact MediaTek for ALPS06419106 specific firmware update if on affected MediaTek-based device
- Check your Android device's security patch level in Settings > About Phone > Security Patch Level
- Contact your device manufacturer or carrier to confirm they have applied MediaTek security patch ALPS06419106
- Apply any available system updates that include the January 2022 Android Security Patch Level or later
- Verify the patch has been applied by re-checking the Security Patch Level after updating
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21759 — 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-21759 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