dbcve.org
AndroidOperating system · Google

CVE-2022-20479

HIGH · 7.8 CVSS v3.1 Published 2022-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
In NotificationChannel of NotificationChannel.java, there is a possible failure to persist permissions settings due to resource exhaustion. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-12 Android-12L Android-13Android ID: A-241764340

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 confidence

In the Android NotificationChannel component, resource exhaustion can cause a failure to properly persist notification permission settings. This could allow a local attacker to escalate privileges by manipulating notification channel permissions without additional execution privileges needed.

MitigationApply the Android security patch (Google's monthly security update) that addresses this vulnerability. Device manufacturers must integrate the framework-level fix into their Android builds.

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
AndroidOperating system
Affected:= 10.0= 11.0= 12.0= 12.1= 13.0

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Android version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Version is 10.0, 11.0, 12.0, 12.1, or 13.0 exactly as listed in affected versions
  2. Check security patch level
    Go to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shell
    Affected if The patch level is earlier than the November 2022 Android security update that addressed this CVE
  3. Verify NotificationChannel is accessible
    Confirm the device runs standard Android framework; NotificationChannel is a system API available on Android 8.0+ and cannot be disabled by users
    Affected if The device is a standard Android environment (not a restricted enterprise profile with disabled notifications) and runs an affected Android version
  4. Confirm no OEM-specific mitigations
    Check with device manufacturer documentation or release notes to see if they integrated the November 2022 framework-level security patch
    Affected if The device manufacturer has not released or applied the specific fix for CVE-2022-20479 in their Android build

A device is affected if it runs Android 10.0, 11.0, 12.0, 12.1, or 13.0 and has not received the November 2022 Android security patch or an equivalent OEM-supplied framework-level fix.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch (Google's monthly security update) that addresses this vulnerability. Device manufacturers must integrate the framework-level fix into their Android builds.

Recommended fix High confidence

December 2022 Android Security Patch Level (or later)

  1. Verify your current Android version by going to Settings > About Phone > Android version
  2. Check for system updates by going to Settings > System > System Update > Check for updates
  3. Install the December 2022 security update or later if available for your device
  4. After updating, verify the patch level by going to Settings > About Phone > Security patch level to confirm the update includes CVE-2022-20479
  5. If your device manufacturer has not released this update, consider checking for quarterly platform releases or contacting your device vendor for patch availability
Caveat Security updates typically have minimal risk; ensure device is charged before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20479 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-20479 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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