dbcve.org
AndroidOperating system · Google

CVE-2022-20200

MEDIUM · 5.5 CVSS v3.1 Published 2022-06-15
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 updateApState of SoftApManager.java, there is a possible leak of hotspot state 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-12LAndroid ID: A-212695058

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 SoftApManager.java, the updateApState method lacks a proper permission check, allowing local applications to access hotspot state information without authorization. This enables local information disclosure of Wi-Fi Access Point configuration and state data.

MitigationApply the Android vendor patch for A-212695058 which adds appropriate permission validation in the SoftApManager.updateApState method to enforce access controls on hotspot state queries.

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:= 12.1

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. Identify Android version
    Go to Settings > About Phone > Android version or run 'getprop ro.build.version.release' via ADB shell
    Affected if Version is 12.1 (exact match)
  2. Check for SoftApManager exposure
    Review installed applications for third-party apps requesting android.permission.WRITE_WIFI_CONFIG or android.permission.ACCESS_WIFI_STATE permissions that are not system utilities
    Affected if Non-system apps hold Wi-Fi configuration or state permissions
  3. Inspect SoftAp configuration access
    Audit app permission grants using 'dumpsys package <package_name>' for any app with SOFT_AP or related Wi-Fi hotspot permissions
    Affected if Apps without system privileges have hotspot-related permissions granted
  4. Review network security logs
    Check Logcat for repeated SoftApManager or hotspot state access attempts from non-system processes: 'logcat -b system | grep -i SoftApManager'
    Affected if Frequent hotspot state queries from third-party applications appear in logs

You are affected if your Android version is exactly 12.1 AND you have third-party applications with Wi-Fi state or hotspot configuration permissions that could query SoftApManager state.

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 vendor patch for A-212695058 which adds appropriate permission validation in the SoftApManager.updateApState method to enforce access controls on hotspot state queries.

Recommended fix High confidence

Android 12L with March 2022 Security Patch Level or later

  1. Apply the March 2022 Android Security Patch Level (SPL) or later to the affected device. This can typically be done through Settings > System > System Update > Check for updates on the device, or through OEM-provided OTA updates.
  2. Verify the patch was applied by checking Settings > About Phone > Android version to confirm the security patch level shows March 2022 or later.
  3. Alternatively, ensure the device receives the monthly security update from your device manufacturer that includes the fix for Android ID A-212695058.

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

Fix this in Android Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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