LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9470: In bff_Scanner_addOutPos of Scanner.c, there is a possible out-of-bounds write due to an incorrect bounds c...

In bff_Scanner_addOutPos of Scanner.c, there is a possible out-of-bounds write due to an incorrect bounds check. This could lead to remote escalation of privilege in an unprivileged app with no additional execution privileges needed. User interaction is needed for exploitation.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9470 is an Android memory safety flaw that could let an attacker elevate privileges through user interaction. The affected code can write outside expected memory bounds. The CVE rates it high severity because successful exploitation could affect confidentiality, integrity, and availability.

Executive priority

Treat this as a high-priority legacy Android exposure issue. The main business risk is unsupported or poorly patched devices, especially where users can install apps or interact with untrusted content.

Technical view

The issue is an out-of-bounds write in bff_Scanner_addOutPos in Scanner.c caused by an incorrect bounds check. The CVE describes remote escalation of privilege from an unprivileged app, with no additional execution privileges required, but user interaction is required.

Likely exposure

Exposure is most likely on Android 7, 8, 8.1, 9, and listed Android development branches that have not received the relevant vendor security update. Managed fleets with legacy Android devices need priority inventory review.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Exploitation is described as requiring user interaction and no pre-existing app privileges, so phishing or malicious-content delivery could be relevant, but details are not provided.

Researcher notes

Evidence is limited to the CVE description, affected Android versions, CWE-787 classification, CVSS 8.8 vector, and Android bulletin reference. Do not assume exploit availability, affected downstream OEM builds, or specific patch levels without vendor confirmation.

Mitigation direction

  • Review Android September 2018 security bulletin and OEM guidance for fixed builds.
  • Prioritize updates for Android 7 through 9 devices still in use.
  • Retire or isolate devices that cannot receive vendor security updates.
  • Restrict installation from untrusted sources on legacy Android devices.
  • Use MDM controls to enforce minimum patch levels where possible.

Validation and detection

  • Inventory Android versions across managed and unmanaged mobile fleets.
  • Check device security patch levels against vendor guidance.
  • Identify Android 7, 8, 8.1, and 9 devices lacking updates.
  • Confirm OEM support status for each affected device model.
  • Review mobile threat telemetry for suspicious app installation activity.
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-9470 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
8.8 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
GoogleAndroid7, 8, 8.1, 9, 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.