CVE-2021-0704
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 createNoCredentialsPermissionNotification and related functions of AccountManagerService.java, there is a possible way to retrieve accounts from the device without permissions due to a permissions bypass. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-9Android ID: A-179338675
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 permissions bypass in Android's AccountManagerService allows local apps to retrieve account information from the device without proper permissions. The vulnerability exists in createNoCredentialsPermissionNotification and related functions where permission checks are not properly enforced, enabling unauthorized access to account data.
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= 9.0= 10.0= 11.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 versionGo to Settings > About Phone > Android version and note the displayed version numberAffected if The version is 9.0, 10.0, or 11.0 (any variant within these major versions)
-
Check security patch levelGo to Settings > About Phone > Security patch level and note the date of the last security updateAffected if The security patch level is earlier than the Google security update that addresses CVE-2021-0704 (compare your patch date to Google's Android security bulletin for February 2021 or later)
-
Identify if device receives Google patchesCheck with your device manufacturer or carrier whether the device is eligible for monthly Android security updatesAffected if The device is no longer receiving security updates or is on an older patch cycle that predates the fix
-
Verify AccountManagerService access controlsOn a rooted device, examine /system/core/accounts.jar or the AOSP source for AccountManagerService.java to confirm the permission check fix is present in createNoCredentialsPermissionNotificationAffected if The installed framework code lacks the permission enforcement fix for this function
A device is affected if it runs Android 9.0, 10.0, or 11.0 and has a security patch level older than the February 2021 Android security update that contains the CVE-2021-0704 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 · scopedApply the Android security patch level that addresses this vulnerability (Android-10, Android-11, Android-9). Device manufacturers must integrate the AOSP fix into their firmware updates.
- 1. Apply the Android security update that addresses this vulnerability. Check your device manufacturer's security bulletin for the specific patch release date.
- 2. On the device, go to Settings > Security > Security update (or Settings > System > Advanced > System update) to verify the installed security patch level.
- 3. Ensure the device has the latest Android security patch level installed. The fix for this vulnerability (Android ID A-179338675) was included in the Android security bulletin for the month it was addressed.
- 4. If the device manufacturer has released a specific update for this CVE, download and install that update through the device's system update mechanism.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-0704 — 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-2021-0704 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