LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9366: In IMSA_Recv_Thread and VT_IMCB_Thread of ImsaClient.cpp and VideoTelephony.c, there is a possible out of b...

In IMSA_Recv_Thread and VT_IMCB_Thread of ImsaClient.cpp and VideoTelephony.c, there is a possible out of bounds write due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9366 is a high-severity Android issue in IMS/video telephony components. A local attacker with low privileges could trigger memory corruption and potentially gain higher privileges. The source says no user interaction is required. Business risk is highest for Android fleets that still run affected vendor security levels or unsupported OEM builds.

Executive priority

Treat as a high-priority legacy Android patching issue. It is not documented as actively exploited in the provided sources, but successful exploitation could elevate local privileges and affect sensitive data, device integrity, and availability.

Technical view

The CVE describes an out-of-bounds write caused by integer overflow in IMSA_Recv_Thread and VT_IMCB_Thread in ImsaClient.cpp and VideoTelephony.c. CVSS 3.1 is 7.8 with local attack vector, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to Android devices or SoC builds containing the affected IMSA and video telephony code identified as SoCVersion. The bundle does not provide specific device models, chipsets, or OEM version ranges.

Exploitation context

The bundle states local escalation of privilege, no additional execution privileges needed, and no user interaction required. It does not cite active exploitation, and KEV status is false, so active exploitation should not be assumed.

Researcher notes

Affected-scope evidence is incomplete: the bundle names Android and SoCVersion but not exact device models or vendor branches. Root cause, impacted threads, file names, privilege requirement, and CVSS impacts are clearly stated.

Mitigation direction

  • Apply the Android June 2018 security bulletin fixes or later applicable OEM updates.
  • Check OEM or SoC vendor guidance for exact affected device and build coverage.
  • Prioritize unsupported Android devices for replacement or isolation.
  • Enforce mobile device management patch compliance for Android security patch levels.

Validation and detection

  • Inventory Android devices and record OEM, model, SoC, and security patch level.
  • Confirm whether devices include the affected IMSA or video telephony components.
  • Compare fleet patch levels against the June 2018 Android bulletin guidance.
  • Review vulnerability scanner results for CVE-2018-9366 without relying on exploit checks.
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-9366 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-9366Attack 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.