CVE-2023-21295
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 SliceManagerService, there is a possible way to check if a content provider is installed due to a missing null check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
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 confidenceA missing null check in SliceManagerService allows local attackers to determine whether a specific content provider is installed on the device. This information disclosure occurs without requiring any special privileges or 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< 14.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 OS versionGo to Settings > About Phone > Android version (or run 'getprop ro.build.version.release' via ADB)Affected if Version is below 14.0 (Android 14)
-
Confirm security patch levelGo to Settings > About Phone > Security patch level (or run 'getprop ro.build.version.security_patch' via ADB)Affected if Patch level is earlier than the June 2023 or subsequent Android security patch that addresses CVE-2023-21295
-
Verify SliceManagerService presenceCheck if the com.android.server.slice.SliceManagerService exists on the device (run 'dumpsys slice' via ADB)Affected if Service is present and responding (confirms the attack surface exists)
-
Confirm no additional enterprise mitigationsReview any enterprise mobility management (EMM) policies or Knox/Work Profile configurations that may restrict slice provider accessAffected if No containerization or policy-based isolation is in place to limit slice access
If the device runs Android version 14.0 or later with the corresponding security patch, the vulnerability is addressed; otherwise, the missing null check in SliceManagerService exposes content provider presence information to local apps without privileges.
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 · scoped14.0
Apply the Android security patch that addresses CVE-2023-21295. Since this is a framework-level vulnerability in SliceManagerService, the fix requires a system update from the device OEM or Google.
Android 14.0
- Upgrade the Android device to version 14.0 or later to obtain the security patch that fixes the missing null check in SliceManagerService
- Verify the Android version by navigating to Settings > About Phone > Android version, confirming it shows 14.0 or higher
- Ensure the latest Android security patch level is applied by checking Settings > Security > Security update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21295 — 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-2023-21295 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