dbcve.org
AndroidOperating system · Google

CVE-2022-24925

MEDIUM · 6.5 CVSS v3.1 Published 2022-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Improper input validation vulnerability in SettingsProvider prior to Android S(12) allows privileged attackers to trigger a permanent denial of service attack on a victim's devices.

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

This vulnerability in Android's SettingsProvider (prior to Android 12) involves improper input validation that allows privileged attackers to cause a permanent denial of service condition. The flaw can be exploited by apps with certain privileges to trigger a state that may require device factory reset to recover.

MitigationApply Android system updates from device OEMs that include the SettingsProvider patch for Android 11 and earlier versions. Users should ensure automatic updates are enabled and install available security patches promptly.

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:= 12.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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 11.0 or earlier (the vulnerability was patched in Android 12)
  2. Verify SettingsProvider accessibility
    Check if apps with privileged access (like WRITE_SECURE_SETTINGS) can modify system settings. Inspect granted permissions via 'dumpsys package <package_name>' for suspicious apps
    Affected if Apps hold WRITE_SECURE_SETTINGS or similar privileged permissions and the Android version is 11 or earlier
  3. Check for DoS indicators
    Look for unresponsive Settings app, missing UI elements in Settings, or 'Permission denied' errors when accessing settings. Check logcat for SettingsProvider crashes: 'logcat | grep SettingsProvider'
    Affected if SettingsProvider crashes occur repeatedly or settings cannot be modified despite appropriate permissions
  4. Confirm SettingsProvider version
    Check system update status in Settings > Security > Google Security Patch level, or via 'getprop ro.build.version.security_patch'
    Affected if Security patch level is earlier than the March 2022 Android Security Bulletin (or patch date is unavailable/older)
  5. Audit privileged apps
    Review installed apps for those requesting SYSTEM_ALERT_WINDOW, WRITE_SECURE_SETTINGS, or signature-level permissions. Use 'dumpsys package permissions' to enumerate
    Affected if Unknown or untrusted third-party apps hold WRITE_SECURE_SETTINGS or other privileged settings permissions on Android 11 or earlier

A user is affected if their device runs Android 11 or earlier and has apps with privileged settings permissions that could trigger the SettingsProvider DoS condition.

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 Android system updates from device OEMs that include the SettingsProvider patch for Android 11 and earlier versions. Users should ensure automatic updates are enabled and install available security patches promptly.

Recommended fix Moderate confidence

Android S (12) or later / Samsung security update containing the fix for this SettingsProvider vulnerability

  1. Check for and apply the latest Android 12 (S) or later system update on the affected device
  2. Alternatively, apply the Samsung security patch that addresses this vulnerability (check Samsung's security update bulletin for the specific patch date)
  3. After updating, verify the SettingsProvider component is running normally
  4. If the device cannot be updated to Android 12, consider contacting Samsung for a backported security patch
Caveat Standard Android 12 upgrade considerations apply (app compatibility, settings changes); review app compatibility before upgrading

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

Fix this in Android Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24925 — 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-24925 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