CVE-2022-47327
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 wlan driver, there is a possible missing permission check. This could lead to local information disclosure.
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 · moderate confidenceA missing permission check in the WLAN driver allows a local attacker with low privileges to access sensitive information they should not have access to. The vulnerability stems from inadequate authorization validation within the wireless driver subsystem, potentially exposing system or network configuration details.
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= 10.0= 11.0= 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.
-
Identify Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shellAffected if The device runs Android 10.0, 11.0, or 12.0 exactly
-
Confirm WLAN is enabledCheck if Wi-Fi is turned on in Settings > Network & Internet > Wi-Fi, or verify the wlan0 interface exists via 'ip link show' in ADB shellAffected if WLAN functionality is present and active on the device
-
Review WLAN driver access patternsCheck system logs (logcat) for unusual or unauthorized WLAN driver ioctl calls or configuration queries from apps without android.permission.ACCESS_WIFI_STATE at elevated verbosityAffected if Low-privilege applications are able to retrieve WLAN configuration data or system details without proper permission validation
-
Audit application permissionsUse 'dumpsys package' via ADB to list granted permissions for installed apps, specifically checking which apps hold ACCESS_WIFI_STATE or related Wi-Fi permissions versus which have accessed WLAN driver dataAffected if Apps without expected Wi-Fi permissions are able to access WLAN driver outputs or sensitive network configuration data
A device is affected if it runs Android 10.0, 11.0, or 12.0 and has WLAN enabled, allowing low-privilege applications to potentially access sensitive Wi-Fi configuration data through the driver due to missing permission checks.
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 dataImplement proper permission checks in the WLAN driver code to validate user privileges before granting access to sensitive operations or data. This typically involves adding authorization logic at driver entry points where sensitive information is accessed or disclosed.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47327 — 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-2022-47327 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