CVE-2021-1014
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 getNetworkTypeForSubscriber of PhoneInterfaceManager.java, 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.Product: AndroidVersions: Android-12Android ID: A-186776740
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 confidenceIn getNetworkTypeForSubscriber of PhoneInterfaceManager.java, a side channel exists that allows a local attacker to determine whether an app is installed on the device without requiring query permissions. This is an information disclosure vulnerability where the network type lookup behavior inadvertently reveals app presence information to any local process.
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= 12.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 versionRun 'getprop ro.build.version.release' via adb shell, or go to Settings > About Phone > Android versionAffected if Version is exactly 12.0 (API level 31)
-
Check security patch levelRun 'getprop ro.build.version.security_patch' via adb shell, or go to Settings > About Phone > Security patch levelAffected if Patch level is earlier than 2022-03-05 (the March 2022 Android security bulletin that includes fix A-186776740)
-
Confirm vulnerability scopeThis is a platform-level framework vulnerability in PhoneInterfaceManager - no application configuration can be checked; detection relies entirely on the system version and patch verification aboveAffected if Device is on Android 12.0 without the platform-level framework fix applied via security update
Device is affected if running Android 12.0 without the March 2022 or later security patch that addresses A-186776740 in PhoneInterfaceManager.
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 (A-186776740) from Google's monthly security bulletin. Organizations should ensure Android-12 devices receive system updates from their OEM/carrier. No application-level code changes can remediate this - it requires the platform-level framework fix.
Latest Android 12 security patch level (check Android Security Bulletin for the specific release containing the fix)
- Apply the latest Android security update for Android 12. Go to Settings > System > Security Update and install any available updates.
- Alternatively, ensure your Android device receives the monthly security patch level that addresses CVE-2021-1014. Check your patch level under Settings > About Phone > Android version.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1014 — 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-1014 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