dbcve.org
AndroidOperating system · Google

CVE-2022-20312

MEDIUM · 5.5 CVSS v3.1 Published 2022-08-12
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 WifiP2pManager, there is a possible toobtain WiFi P2P MAC address without user consent due to missing permission check. This could lead to local information disclosure without additional execution privileges needed. User interaction is not needed forexploitationProduct: AndroidVersions: Android-13Android ID: A-192244925

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's WifiP2pManager, a missing permission check allows any local application to retrieve the WiFi P2P MAC address without requiring user consent or special privileges. The MAC address is exposed through the system service without validating that the caller has appropriate permissions, enabling unauthorized information disclosure.

MitigationApply the Android security patch that addresses A-192244925, which adds proper permission validation before disclosing WiFi P2P MAC addresses. Until the patch is available, monitor app permissions and limit granting of ACCESS_WIFI_STATE to trusted applications.

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:= 13.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
    Navigate to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if Version equals 13.0 - this places the device in the affected product range
  2. Identify apps with ACCESS_WIFI_STATE permission
    Use ADB command: 'dumpsys package <package_name>' to inspect permissions for installed apps, or check via Settings > Apps > Permissions
    Affected if Any untrusted or unknown applications hold ACCESS_WIFI_STATE permission, which could be exploited to retrieve the WiFi P2P MAC address
  3. Verify WifiP2pManager service accessibility
    Test whether an application without elevated privileges can successfully call getMacAddress() on WifiP2pManager and receive a MAC address response
    Affected if The call returns a valid MAC address without throwing a SecurityException, indicating the permission check is missing
  4. Review app permission grants
    Run 'pm list permissions android.permission.ACCESS_WIFI_STATE' via ADB to see all granted permission instances
    Affected if Applications other than system apps or trusted wifi utilities have been granted this permission

A device is affected if it runs Android 13.0 and contains applications that can access the WifiP2pManager without proper permission validation, allowing unauthorized disclosure of the WiFi P2P MAC address.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Android security patch that addresses A-192244925, which adds proper permission validation before disclosing WiFi P2P MAC addresses. Until the patch is available, monitor app permissions and limit granting of ACCESS_WIFI_STATE to trusted applications.

Recommended fix Moderate confidence

Android 14 (or later Android 13 security patch level containing the September 2022 Android Security Bulletin fixes)

  1. Check your Android device's security patch level in Settings > About Phone > Security Patch Level
  2. Verify if your device has received the September 2022 Android Security Bulletin or later updates
  3. If available, install any pending system updates for your Android 13 device
  4. If your device manufacturer has not released a security patch containing the fix (CVE-2022-20312), consider upgrading to Android 14 which includes this security fix
  5. For enterprise or managed devices, consult your device administrator or mobile device management (MDM) console for available system updates
Caveat Android 14 may have behavior changes and app compatibility considerations; review release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-20312 — 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-2022-20312 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