dbcve.org
AndroidOperating system · Google

CVE-2021-0597

MEDIUM · 5.5 CVSS v3.1 Published 2021-07-14
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 notifyProfileAdded and notifyProfileRemoved of SipService.java, there is a possible way to retrieve SIP account names due to 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-8.1 Android-9 Android-10 Android-11Android ID: A-176496502

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 notifyProfileAdded and notifyProfileRemoved of SipService.java, missing permission checks allow any local application to retrieve SIP account names without authorization, leading to local information disclosure.

MitigationThis requires a vendor patch to add proper permission validation in the SIP service notification methods. Users should apply Android security updates.

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:= 8.1= 9.0= 10.0= 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. Check Android version
    Go to Settings > About Phone > Android version or run 'getprop ro.build.version.release' in ADB shell
    Affected if Version is 8.1, 9.0, 10.0, or 11.0 - the device falls within the affected version range
  2. Determine if SIP service is in use
    Check if the device has SIP-based calling enabled: go to Settings > Connections > Wi-Fi Calling (or Settings > Phone > Calls > SIP call settings on some devices), or inspect /data/data/com.android.phone/databases/ for SIP-related data
    Affected if SIP accounts or profiles are configured on the device - the vulnerable methods notifyProfileAdded/notifyProfileRemoved only expose data if SIP accounts exist
  3. Identify apps with SIP query capability
    Review installed applications for those with permission to interact with SipService - check for apps requesting android.permission.USE_SIP or android.permission.READ_PHONE_STATE, or monitor logcat for SipService calls
    Affected if Any installed application can invoke the vulnerable SipService methods without proper permission checks - no special app configuration is required for the flaw to apply
  4. Audit SipService notification methods
    Decompile or inspect the framework JAR at /system/framework/framework.jar (classes.dex or com/android/internal/telephony/SipService.smali) to verify if notifyProfileAdded or notifyProfileRemoved methods contain ENFORCE_PHONE_PERMISSION or similar permission checks
    Affected if The code lacks proper permission validation in these notification methods - exploitation requires no special configuration beyond running the affected Android version

A user is affected if their device runs Android 8.1, 9.0, 10.0, or 11.0 and has SIP accounts or profiles configured, as the missing permission checks in SipService expose account names to any local application.

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

This requires a vendor patch to add proper permission validation in the SIP service notification methods. Users should apply Android security updates.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-0597 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-0597 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