CVE-2023-21396
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 Activity Manager, there is a possible background activity launch due to a logic error in the code. This could lead to local escalation of privilege with User 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 · high confidenceA logic error in Android's Activity Manager allows launching background activities without user visibility, enabling a malicious application to perform actions in the background without user interaction. This leads to local privilege escalation by bypassing activity launch restrictions designed to prevent unauthorized background activity starts.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check Android OS versionGo to Settings > About Phone > Android version. This displays the current Android OS version.Affected if The Android version is below 14.0 (Android 14) and the Security Patch Level is not up to date.
-
Check Security Patch LevelGo to Settings > About Phone > Security patch level. This shows the date of the installed Android security updates.Affected if The Security Patch Level is earlier than the patch that includes the fix for CVE-2023-21396 (refer to Google's Android Security Bulletin for the specific month).
-
Verify Activity Manager componentThe vulnerability exists in the Activity Manager service (activity service). This is a core Android system component; no specific module enablement is required.Affected if The device runs a vulnerable Android version (below 14.0) with an outdated Security Patch Level.
-
Confirm patch inclusion via vendorCheck with your device manufacturer or carrier to confirm that the specific CVE-2023-21396 fix has been included in the installed Security Patch Level.Affected if The manufacturer has not released or applied the security update containing the CVE-2023-21396 fix.
The device is affected if it runs Android version below 14.0 AND has a Security Patch Level older than the update that includes the CVE-2023-21396 fix.
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 level (SPL) that includes the CVE-2023-21396 fix from Google's monthly security bulletin. This is typically handled through device manufacturer OTA updates.
Android 14.0
- Upgrade the Android device to version 14.0 or later to receive the fix for this privilege management vulnerability in Activity Manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21396 — 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-21396 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