LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9410: In analyzeAxes of FontUtils.cpp, there is a possible out of bounds read due to a missing bounds check.

In analyzeAxes of FontUtils.cpp, 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.

MediumCVSS 5.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-9410 is an Android memory read flaw in font handling. On affected Android 8 and 8.1.0 devices, a local low-privileged attacker could potentially expose sensitive information. The sources do not show code execution, system takeover, or active exploitation.

Executive priority

Treat this as a moderate legacy Android hygiene issue. It matters for fleets still running Android 8 or 8.1.0, especially where sensitive data is present, but sources do not support emergency response.

Technical view

The issue is a CWE-125 out-of-bounds read in analyzeAxes of FontUtils.cpp caused by a missing bounds check. CVSS 3.1 is 5.5 with local attack vector, low complexity, low privileges, no user interaction, and high confidentiality impact only.

Likely exposure

Exposure is mainly legacy Android 8 and 8.1.0 devices that lack the relevant Google or OEM security update. Other versions are not listed as affected in the source bundle.

Exploitation context

The CVSS vector indicates local access and low privileges are required, with no user interaction. CISA KEV status is false, and the provided sources do not cite active exploitation.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, affected Android versions, and Google's bulletin reference. No exploit details, proof-of-concept, or active exploitation claims are provided in the source bundle.

Mitigation direction

  • Inventory Android 8 and 8.1.0 devices in managed fleets.
  • Apply Google or OEM security updates covering the July 2018 Android bulletin.
  • Retire or isolate unsupported devices that cannot receive vendor fixes.
  • Check vendor guidance before applying compensating controls.

Validation and detection

  • Confirm device Android versions and security patch levels.
  • Compare patch status with Google's July 2018 Android Security Bulletin.
  • Prioritize unmanaged or unsupported Android 8 and 8.1.0 assets.
  • Record remediation evidence from MDM, EMM, or asset inventory data.
Prepared
Confidence
high
Sources
3

Public sources used

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.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-9410 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2018-9410Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid8, 8.1.0unaffected
Weakness

CWE details

CWE-125

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs