LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9370: In download.c there is a special mode allowing user to download data into memory and causing possible memor...

In download.c there is a special mode allowing user to download data into memory and causing possible memory corruptions due to missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9370 is an Android-related memory corruption issue in download.c. A missing bounds check in a special memory-download mode could allow local privilege escalation. The business concern is affected Android device fleets, especially vendor or SoC builds that missed the June 2018 Android security bulletin updates.

Executive priority

Treat as a high-priority legacy Android fleet hygiene issue, not an internet-exposed emergency based on available evidence. Risk is highest where old or unsupported Android devices remain in privileged operational environments.

Technical view

The CVE describes CWE-787 out-of-bounds write risk in download.c, triggered by a special mode that downloads data into memory without adequate bounds checking. Impact is local privilege escalation with high confidentiality, integrity, and availability impact. Public metadata is limited and inconsistent on user interaction.

Likely exposure

Exposure appears limited to Android devices or SoC/vendor firmware containing the affected download.c implementation. The supplied affected entry names Google Android and SoCVersion, but does not identify specific device models, chipset vendors, or version ranges.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The CVE text says user interaction is needed, while the CVSS vector says UI:N, so exploitation prerequisites are unclear from the provided sources.

Researcher notes

The public record is sparse: affected version data is not granular, and interaction requirements conflict between description and CVSS. Avoid assuming broad Android exposure without firmware lineage or OEM bulletin confirmation.

Mitigation direction

  • Apply Android Security Bulletin June 2018 fixes where applicable.
  • Confirm OEM firmware includes the relevant Android security patch level.
  • Prioritize unsupported Android or embedded devices for replacement planning.
  • Check vendor advisories for device-specific remediation details.

Validation and detection

  • Inventory Android devices, firmware versions, and security patch levels.
  • Map device OEM bulletins to CVE-2018-9370 coverage.
  • Flag devices missing June 2018 Android security updates.
  • Review EMM/MDM data for unsupported Android builds.
Prepared
Confidence
medium
Sources
3

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-787: 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-9370 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2018-9370Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroidSoCVersionunaffected
Weakness

CWE details

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

CWE-787 · source CWE mapping

Out-of-bounds Write

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