dbcve.org
AndroidOperating system · Google

CVE-2023-20975

HIGH · 7.8 CVSS v3.1 Published 2023-03-24
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 getAvailabilityStatus of EnableContentCapturePreferenceController.java, there is a possible way to bypass DISALLOW_CONTENT_CAPTURE due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-250573776

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

A permissions bypass in the getAvailabilityStatus method of EnableContentCapturePreferenceController.java on Android-13 allows bypassing the DISALLOW_CONTENT_CAPTURE restriction, enabling local privilege escalation without user interaction or additional execution privileges.

MitigationApply the Android security patch for Android-13 that addresses this vulnerability in the EnableContentCapturePreferenceController. Users should ensure their devices receive latest security updates.

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:= 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 is exactly 13.0
    Run 'getprop ro.build.version.release' or navigate to Settings > About Phone > Android version
    Affected if The version shows exactly 13.0 (not 13.0.1, 13.0.2, or later)
  2. Verify DISALLOW_CONTENT_CAPTURE restriction capability
    Check device policy or restriction settings for content capture - on a managed device, inspect DevicePolicyManager getUserRestrictions or look for DISALLOW_CONTENT_CAPTURE in /data/system/users/0/runtime-permissions.xml
    Affected if The DISALLOW_CONTENT_CAPTURE restriction is enabled but can be bypassed via EnableContentCapturePreferenceController
  3. Identify EnableContentCapturePreferenceController accessibility
    Check if the Settings app or EnableContentCapturePreferenceController component is accessible to apps via intents or content providers - inspect package:com.android.settings and look for the EnableContentCapturePreferenceController class
    Affected if The controller is exposed and accessible without proper permission validation on Android 13.0

A device is affected only if it is running Android version 13.0 exactly and has the DISALLOW_CONTENT_CAPTURE restriction mechanism that can be bypassed through EnableContentCapturePreferenceController.

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 for Android-13 that addresses this vulnerability in the EnableContentCapturePreferenceController. Users should ensure their devices receive latest security updates.

Recommended fix High confidence

Android 13 with Security Patch Level June 2023 or later (Android-13 baseband, refer to device manufacturer's security bulletin)

  1. 1. Navigate to Settings on the Android device
  2. 2. Scroll down and tap on 'Security & privacy' or 'Privacy'
  3. 3. Tap on 'Security' or 'More security settings'
  4. 4. Tap on 'Security update' or 'Android security update'
  5. 5. Check the current security patch level and ensure it includes the fix for CVE-2023-20975
  6. 6. If an update is available, tap 'Download and install' to apply the latest Android security patch

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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