CVE-2019-9243
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 wpa_supplicant_8, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Product: AndroidVersions: Android-10Android ID: A-120905706
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 confidenceAn out-of-bounds read vulnerability exists in wpa_supplicant_8 due to a missing bounds check, allowing local information disclosure without elevated privileges or user interaction. The flaw is in the Wi-Fi protection access daemon used by Android-10.
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.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.
-
Confirm Android version is 10.0Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if The device is running Android 10.0 exactly (version code Q) or any Android 10 build prior to the security patch
-
Identify wpa_supplicant versionRun 'wpa_supplicant -v' or check via 'getprop persist.service.wpa.supplicant' or inspect /system/bin/wpa_supplicantAffected if The wpa_supplicant version is earlier than the patched build for Android 10 (the vulnerable version is wpa_supplicant_8 included with Android 10)
-
Verify Wi-Fi functionality is presentCheck if Wi-Fi hardware and software stack are available on the device - confirm wpa_supplicant daemon exists on the systemAffected if Wi-Fi is enabled and wpa_supplicant_8 is running as the Wi-Fi daemon (the out-of-bounds read occurs in this daemon during Wi-Fi operations)
-
Check for security patch levelGo to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if The security patch level is earlier than the February 2019 (or subsequent) Android security update that addresses this CVE
A device is affected if it runs Android 10.0 with a wpa_supplicant_8 Wi-Fi daemon and has a security patch level prior to the CVE fix, making local information disclosure possible via the out-of-bounds read during Wi-Fi operations.
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 Android-10 that addresses the bounds check issue in wpa_supplicant_8. Users should update their Android devices to the patched version.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9243 — 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-9243 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