CVE-2018-9384

MEDIUMNVD 4.44.4—Trending — 3 sources updated this week

4.4

In multiple locations, there is a possible way to bypass KASLR due to an unusual root cause. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.

CVSS v3: 4.4
EG Score: 4.4(medium)
EPSS: 0.1%
KEV: Not listed

Published

January 17, 2025

Last Modified

July 10, 2025

References (1)

security@androidhttps://source.android.com/security/bulletin/pixel/2018-06-01

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 6× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-01 13:50 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-30 13:08 UTCEG score recompute
2026-05-30 13:08 UTCGHSA enrichment
2026-05-29 13:41 UTCepss_batch

Frequently asked(5)

What is CVE-2018-9384?

CVE-2018-9384 is a medium vulnerability published on January 17, 2025. In multiple locations, there is a possible way to bypass KASLR due to an unusual root cause. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.

When was CVE-2018-9384 disclosed?

CVE-2018-9384 was first published in the National Vulnerability Database on January 17, 2025, with the most recent update on July 10, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2018-9384 actively exploited?

CVE-2018-9384 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2018-9384?

CVE-2018-9384 has a CVSS v3 base score of 4.4 (NVD).

How do I remediate CVE-2018-9384?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-9384, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-9384

Explore →

Is Your Infrastructure Affected by CVE-2018-9384?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2018-9384

📅 Published

🔄 Last Modified

🔗 References (1)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2018-9384?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (1)

Frequently asked(5)

Related CVEs(same CWE)