CVE-2020-0378
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 onWnmFrameReceived of PasspointManager.java, there is a missing permission check. This could lead to local information disclosure of location data with User execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-9 Android-10 Android-11Android ID: A-157748906
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 missing permission check in PasspointManager.java's onWnmFrameReceived method allows local applications with basic user privileges to access location data (from WNM frames) without proper authorization, enabling unauthorized location information disclosure.
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 version installed on the deviceRun 'adb shell getprop ro.build.version.release' or check Settings > About Phone > Android versionAffected if The version reported is 9.0, 10.0, or 11.0 exactly (not later security patch levels)
-
Verify the PasspointManager component existsCheck for the presence of PasspointManager in the Android framework: 'adb shell pm list packages | grep -i passpoint' or inspect the framework JAR at /system/framework/framework.jarAffected if The PasspointManager component is present in the Android system (this is true for all affected versions)
-
Confirm no permission enforcement on onWnmFrameReceivedInspect the decompiled PasspointManager.java and locate the onWnmFrameReceived method; verify it lacks an ACCESS_FINE_LOCATION permission check or enforceCallingPermission callAffected if The method contains no permission verification before processing WNM frame location data (requires source code or decompiled APK inspection)
-
Test for unauthorized location data accessInstall a basic user-privilege app and attempt to trigger PasspointManager's onWnmFrameReceived callback to see if location data from WNM frames is returned without permission denialAffected if Location data from WNM frames is returned to the app without the system throwing a SecurityException for missing ACCESS_FINE_LOCATION
A device is affected if it runs Android 9.0, 10.0, or 11.0 and the PasspointManager's onWnmFrameReceived method processes location data without verifying the ACCESS_FINE_LOCATION permission.
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.
From vendor dataApply the Android security patch for this vulnerability; the fix requires adding appropriate permission verification (e.g., ACCESS_FINE_LOCATION check) in the affected PasspointManager method.
- Consultation6.0 h
- Implementation3.0 h
- Testing12.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,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-0378 — 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-2020-0378 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