AndroidOperating system · Google

CVE-2021-0554

MEDIUM · 5.5 CVSS v3.1 Published 2021-06-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 isBackupServiceActive of BackupManagerService.java, there is a missing permission check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11Android ID: A-158482162

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 confidence

In Android-11, the BackupManagerService's isBackupServiceActive method lacks a permission check, allowing any local process to query backup service status without authorization. This enables local information disclosure where an app can determine whether backup services are active, potentially revealing sensitive backup-related configuration or operational state.

MitigationApply a permission check (typically CHECK_BACKUP_PERMISSION or equivalent) to the isBackupServiceActive method in BackupManagerService.java to ensure only authorized callers can query backup service status.

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:= 11.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Android version
    Check the device or system settings to confirm the Android version is exactly 11.0. On most devices, this is found under Settings > About Phone > Android version.
    Affected if The Android version is 11.0 (exact match)
  2. Confirm BackupManagerService presence
    Locate the BackupManagerService component in the Android system. This is typically found in the system service layer as part of the Android backup framework.
    Affected if BackupManagerService is present and running on the device
  3. Check isBackupServiceActive method accessibility
    Examine the BackupManagerService implementation or conduct a code audit to verify whether the isBackupServiceActive method enforces any permission check before returning backup service status.
    Affected if The isBackupServiceActive method lacks a permission check (such as CHECK_BACKUP_PERMISSION) and is callable by any local process
  4. Test backup service status query
    Use a test application or ADB command to attempt calling the isBackupServiceActive method from a non-privileged process to determine if it returns backup service status without authorization.
    Affected if A non-privileged app can successfully query backup service status without any permission error
  5. Review app permissions on the device
    Inspect installed applications to identify any untrusted or potentially malicious apps that have the capability to query system services.
    Affected if Any installed application can invoke the unprotected isBackupServiceActive method to reveal backup operational state

A device is affected if it runs Android 11.0 and the isBackupServiceActive method in BackupManagerService can be called by any local process without permission checks.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply a permission check (typically CHECK_BACKUP_PERMISSION or equivalent) to the isBackupServiceActive method in BackupManagerService.java to ensure only authorized callers can query backup service status.

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-0554 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-0554 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