CVE-2018-9388

Google Android vulnerability

9.8 CRITICALEPSS 0.16%

Published5 Dec 2024

Description

In store_upgrade and store_cmd of drivers/input/touchscreen/stm/ftm4_pdc.c, there are out of bound writes due to missing bounds checks or integer underflows. These could lead to escalation of privilege.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Google Androidall versions

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

Frequently asked

Is CVE-2018-9388 being actively exploited?

CVE-2018-9388 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.16%.

How severe is CVE-2018-9388?

CVE-2018-9388 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.16% probability of exploitation.

Which products are affected by CVE-2018-9388?

Affected products include Google Android.

How do I fix CVE-2018-9388?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2018-9388 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.