CVE-2019-2053
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 wnm_parse_neighbor_report_elem of wnm_sta.c, there is a possible out-of-bounds read due to missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android Versions: Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9 Android ID: A-122074159
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 confidenceAn out-of-bounds read vulnerability exists in the wnm_parse_neighbor_report_elem function in wnm_sta.c due to a missing bounds check. When parsing Wi-Fi Neighbor Report elements, the code reads memory beyond the allocated buffer, potentially exposing sensitive kernel memory contents to local attackers without requiring any privileges or user interaction.
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= 7.0= 7.1.1= 7.1.2= 8.0= 8.1= 9.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.0/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.
-
Confirm Android version is within affected rangeGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell. Check if the version equals 7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0Affected if Android version is exactly 7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0
-
Verify Wi-Fi functionality is enabledCheck if Wi-Fi is turned on in Settings > Network & Internet > Wi-Fi, or run 'settings get global wifi_on' via ADB shellAffected if Wi-Fi is enabled on the device, as the vulnerable code path in wnm_sta.c is only reached when parsing Neighbor Report elements during Wi-Fi operations
-
Check Android security patch levelGo to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADB shell. Compare the date to the patch release for this CVE (March 2019)Affected if Security patch level is earlier than March 2019 or the device has not received the CVE-2019-2053 patch
-
Inspect wpa_supplicant version if accessibleRun 'wpa_supplicant -v' or 'wpa_cli status' via ADB shell to identify the wpa_supplicant versionAffected if wpa_supplicant version is older than the patched version containing the bounds check fix in wnm_parse_neighbor_report_elem
The device is affected if it runs Android 7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0, has Wi-Fi enabled, and has not received the March 2019 Android security patch or later that addresses CVE-2019-2053.
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 upstream patch which adds proper bounds validation before accessing the neighbor report element data. Since this is a kernel-space Wi-Fi driver vulnerability in Android, the fix requires updating the Android system image with the patched wpa_supplicant/hostapd or kernel Wi-Fi stack components.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-2053 — 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-2019-2053 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