LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9340: In ResStringPool::setTo of ResourceTypes.cpp, it's possible for an attacker to control the value of mString...

In ResStringPool::setTo of ResourceTypes.cpp, it's possible for an attacker to control the value of mStringPoolSize to be out of bounds, causing information disclosure.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9340 is an Android platform information disclosure flaw. A remote, unauthenticated attacker may be able to trigger out-of-bounds behavior in Android resource parsing and expose sensitive information. The sources do not identify active exploitation or provide a standalone mitigation beyond Android vendor guidance.

Executive priority

Prioritize remediation where affected Android versions remain in production, especially on devices handling sensitive data. Treat this as legacy platform risk unless evidence shows current exposure in your fleet.

Technical view

The flaw is in ResStringPool::setTo in ResourceTypes.cpp. Attacker-controlled mStringPoolSize can go out of bounds, causing information disclosure. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, mapped to CWE-787.

Likely exposure

Exposure is limited to listed Google Android versions: 6, 6.0.1, 7, 8, 8.1, nyc-mr1-dev, and nyc-mr2-dev. Other versions are not identified as affected in the provided record.

Exploitation context

The source bundle does not report known active exploitation, and the CVE is not marked KEV. The CVSS vector indicates network reachability, low complexity, no required privileges, and no user interaction, but the exact reachable product surface is not described.

Researcher notes

The record names information disclosure only; no integrity or availability impact is claimed. Do not assume exploit availability, affected components beyond ResourceTypes.cpp, or fixes beyond the referenced Android bulletin without additional vendor evidence.

Mitigation direction

  • Review the Android June 2018 security bulletin for vendor guidance.
  • Apply applicable Google or OEM Android security updates.
  • Retire or isolate affected Android versions that cannot be updated.
  • Track OEM patch availability for managed Android fleets.

Validation and detection

  • Inventory Android versions across managed devices and builds.
  • Confirm whether devices run Android 6 through 8.1 or listed dev branches.
  • Verify installed security patch level against vendor guidance.
  • Document unsupported devices that cannot receive relevant updates.
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-9340 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.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid6, 6.0.1, 7, 8, 8.1, nyc-mr1-dev, nyc-mr2-devunaffected
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.