LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9593: In llcp_dlc_proc_i_pdu of llcp_dlc.cc in Android-7.0, Android-7.1.1, Android-7.1.2, Android-8.0, Android-8....

In llcp_dlc_proc_i_pdu of llcp_dlc.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 incorrect bounds check. 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-116722267.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This Android NFC flaw could let a nearby attacker read information from affected devices without user interaction. The sources identify Android 7.0 through 9 as affected. Business risk is highest for legacy or unmanaged devices that still have NFC enabled and lack the January 2019 Android security updates. Exposure is most likely on unpatched Android 7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9 devices with NFC enabled. Modern patched devices are less likely to be exposed, but legacy enterprise phones, tablets, kiosks, or unmanaged BYOD devices should be checked. Treat this as a moderate legacy mobile risk. It is not evidenced as actively exploited in the provided sources, but unpatched NFC-enabled devices can create avoidable information-disclosure exposure, especially in public-facing, shared, or unmanaged environments. Mitigation focus: Apply Android security updates from the January 2019 bulletin or later vendor guidance.; Retire or isolate devices that cannot receive relevant vendor security updates.; Disable NFC on affected devices where business use does not require it..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-9593 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AndroidAndroidAndroid-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.