LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9478: In process_service_attr_req and process_service_search_attr_req of sdp_server.cc, there is an out of bounds...

In process_service_attr_req and process_service_search_attr_req of sdp_server.cc, there is an out of bounds write due to a missing bounds check. This could lead to remote code execution with no additional execution privileges needed.  User interaction is not needed for exploitation.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2018-9478 is a critical Android flaw where crafted service attribute requests can trigger an out-of-bounds write. The stated impact is remote code execution without privileges or user interaction. This matters most for older or unpatched Android 7, 8, 8.1, and 9 devices.

Executive priority

Treat this as high-priority legacy Android risk. The impact is severe, but urgency depends on whether affected, unpatched devices remain in the environment. Focus on inventory, patch confirmation, and retirement of devices that cannot receive vendor fixes.

Technical view

The issue is CWE-787 in Android sdp_server.cc, affecting process_service_attr_req and process_service_search_attr_req. A missing bounds check can cause an out-of-bounds write. CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely in fleets containing Android 7, 8, 8.1, or 9 devices that missed the September 2018 Android security fixes or OEM-equivalent updates.

Exploitation context

The source bundle states remote code execution is possible without privileges or user interaction. It does not show CISA KEV listing, active exploitation, public exploit availability, or observed attacks, so exploitation-in-the-wild is not established here.

Researcher notes

Evidence is limited to the CVE record and Android bulletin reference. The affected functions indicate bounds-check failure in SDP request handling, but the supplied sources do not provide patch diffs, proof-of-concept details, exploit telemetry, or vendor-specific downstream status.

Mitigation direction

  • Apply Android September 2018 security bulletin fixes or later OEM security updates.
  • Prioritize unsupported Android 7 through 9 devices for replacement or isolation.
  • Check vendor guidance for device-specific patch availability and update paths.
  • Reduce exposure of unpatched devices where patching is not possible.
  • Track remediation by Android security patch level, not only OS version.

Validation and detection

  • Inventory Android devices and record OS version and security patch level.
  • Identify devices running Android 7, 8, 8.1, or 9.
  • Confirm whether September 2018 or later security fixes are installed.
  • Review MDM or EMM compliance data for unmanaged legacy devices.
  • Document unsupported devices needing compensating controls or retirement.
Prepared
Confidence
high
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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-9478 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2018-9478Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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