CVE-2023-21344
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 Job Scheduler, there is a possible way to determine whether an app is installed, without query permissions, due to side channel information disclosure. 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 confidenceThis is an Android platform vulnerability in the JobScheduler component that allows a local attacker to determine if a specific app is installed without requiring query permissions. The side channel disclosure likely exploits observable differences in JobScheduler behavior (timing, error responses, or job existence checks) when attempting to schedule jobs for non-existent apps versus existing ones.
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 the Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The version shown is less than 14.0 (Android 14)
-
Verify JobScheduler service availabilityRun 'dumpsys jobscheduler' via ADB shell to confirm the service is active and respondingAffected if JobScheduler is running and accessible on the device
-
Check if third-party apps can access JobSchedulerReview app permissions in Settings > Apps > [target app] > Permissions; verify if the app has JOB_SCHEDULER permission or can bind to the JobScheduler serviceAffected if Apps without QUERY_ALL_PACKAGES permission can schedule jobs and potentially probe for other app installations
A device is affected if it runs Android version 13 or lower, as the side-channel in JobScheduler allows any local app to detect whether other specific apps are installed without proper permissions.
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 Android system security updates; this is an OS-level vulnerability that requires patching by Google in monthly security bulletins. Users should ensure devices receive timely platform updates.
Android 14.0 (Upside Down Cake) or later
- Verify the current Android version on the device by going to Settings > About Phone > Android version
- Check if Android 14.0 (Upside Down Cake) or later is available for your specific device model
- If available, initiate the system update through Settings > System > Software Update > Check for updates
- Alternatively, manually flash the factory image for Android 14.0 or later if your device manufacturer provides it
- After updating, verify the fix is applied by confirming the Android version shows 14.0 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21344 — 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-21344 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