LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9367: In FT_ACDK_CCT_V2_OP_ISP_SET_TUNING_PARAS of Meta_CCAP_Para.cpp, there is a possible out of bounds write du...

In FT_ACDK_CCT_V2_OP_ISP_SET_TUNING_PARAS of Meta_CCAP_Para.cpp, there is a possible out of bounds write due to improper input validation. 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-9367 is a high-severity Android local privilege escalation issue. A local attacker with low privileges could trigger an out-of-bounds write without user interaction, potentially gaining higher control over confidentiality, integrity, and availability on affected devices.

Executive priority

Treat as high priority for Android fleets that may still include older or unsupported devices. The risk is local rather than remote, but successful exploitation could materially compromise a device.

Technical view

The issue is an improper input validation flaw in FT_ACDK_CCT_V2_OP_ISP_SET_TUNING_PARAS within Meta_CCAP_Para.cpp, causing a possible out-of-bounds write. CVSS 3.1 is 7.8: local attack vector, low complexity, low privileges, no user interaction, and high impact across CIA.

Likely exposure

Exposure appears limited to Android device builds or SoC-related components covered by the Android June 2018 security bulletin. The provided affected-version detail is only “SoCVersion,” so exact model and firmware scope requires vendor or OEM confirmation.

Exploitation context

The supplied sources do not show active exploitation, and this CVE is not listed as KEV. Exploitation is local, requires low privileges, and does not require user interaction, which matters most on devices where untrusted local apps can run.

Researcher notes

The public record gives function, file, weakness type, and CVSS, but not detailed affected models or exploit evidence. Avoid broad product claims beyond Android and SoCVersion unless confirmed by OEM bulletins.

Mitigation direction

  • Apply Android or OEM updates covering the June 2018 security bulletin.
  • Confirm affected device models and firmware with vendor or OEM advisories.
  • Prioritize unsupported Android devices for replacement or isolation.
  • Restrict installation of untrusted apps on potentially affected devices.
  • Monitor vendor guidance for any product-specific remediation details.

Validation and detection

  • Inventory Android devices, OS builds, patch levels, and SoC details.
  • Check whether devices include the June 2018 Android security bulletin fixes.
  • Map affected assets against vendor or OEM CVE advisories.
  • Review vulnerability scanner findings for CVE-2018-9367 carefully.
  • 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-9367 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-9367Attack 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.