CVE-2018-9594
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 llcp_link_proc_agf_pdu of llcp_link.cc in Android-7.0, Android-7.1.1, Android-7.1.2, Android-8.0, Android-8.1 and Android-9, there is a possible out of bounds read due to an integer overflow. This could lead to local information disclosure over NFC with no additional execution privileges needed. User interaction is not needed for exploitation. Android ID: A-116791157.
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 vulnerability exists in Android's NFC LLCP (Logical Link Control Protocol) stack where an integer overflow in the llcp_link_proc_agf_pdu function in llcp_link.cc leads to an out-of-bounds memory read. This occurs when processing AGF (Aggregated Frame) PDUs, allowing a local attacker to potentially read sensitive information from memory over NFC without any user interaction or elevated privileges.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:A/AC:L/PR:N/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.
-
Verify NFC is enabled on the deviceNavigate to Settings > Network & Internet (or Connections) > NFC, or check the quick settings panel for the NFC icon. On the command line, use 'settings get global nfc_on' or check /proc/self/mountinfo for nfc-related mounts.Affected if NFC is enabled and the device has NFC hardware. If NFC is disabled, the attack surface is not present.
-
Check the installed Android versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via adb shell.Affected if The Android version matches exactly 7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0. Versions outside this range (e.g., 10.0+) or different minor versions are not affected by this specific CVE.
-
Check the Android security patch levelGo to Settings > About Phone > Security patch level, or run 'getprop ro.build.version.security_patch' via adb shell.Affected if The security patch level is earlier than the patch that addresses CVE-2018-9594. The fix was included in Google's monthly Android Security Bulletin for the month the patch was released. Compare your patch date to the bulletin release date for this CVE.
The device is affected if NFC is enabled, the Android version is exactly one of 7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0, and the security patch level predates the fix for CVE-2018-9594.
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 level that addresses CVE-2018-9594 (released in Google's monthly Android Security Bulletins). Users should update their devices to a patched Android version (Android 7.0+ to Android 9). There is no application-level code fix; this requires a platform-level system update.
- Consultation2.0 h
- Testing4.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-9594 — 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-2018-9594 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