LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9378: In BnAudioPolicyService::onTransact of IAudioPolicyService.cpp, there is a possible information disclosure...

In BnAudioPolicyService::onTransact of IAudioPolicyService.cpp, there is a possible information disclosure due to uninitialized data. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

MediumCVSS 6.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-9378 is an Android information disclosure issue. A local attacker may read sensitive memory data without user interaction or extra privileges. The business impact is confidentiality loss on affected Android devices, not system takeover or service outage based on the provided sources.

Executive priority

Treat as a moderate confidentiality risk for Android fleets. It warrants normal patch governance, with higher priority for executives, regulated users, and devices processing sensitive data. There is no provided evidence of active exploitation.

Technical view

The flaw is uninitialized data exposure in BnAudioPolicyService::onTransact in IAudioPolicyService.cpp, classified as CWE-908. CVSS 3.1 is 6.2: local attack vector, low complexity, no privileges, no user interaction, high confidentiality impact, no integrity or availability impact.

Likely exposure

Exposure appears limited to Android devices matching the CVE record's Android Kernel affected entry and relevant vendor bulletin scope. The provided sources do not identify exact device models, build numbers, or OEM backport status.

Exploitation context

The source bundle states local exploitation is possible without user interaction or additional privileges. It does not cite active exploitation, public exploit availability, or CISA KEV listing, so active exploitation should not be assumed.

Researcher notes

Evidence is sparse: the CVE describes the vulnerable function, impact, CVSS vector, CWE, and one Pixel bulletin reference. It does not provide exact affected build ranges, patch identifiers, exploit indicators, or detailed remediation beyond vendor guidance.

Mitigation direction

  • Check the Android/Pixel June 2018 bulletin and OEM advisories for applicable fixed builds.
  • Prioritize updates for managed Android devices handling sensitive business data.
  • Verify mobile device management policies require supported, patched Android builds.
  • Replace or isolate unsupported devices that cannot receive vendor security updates.

Validation and detection

  • Inventory Android device models, Android versions, and security patch levels.
  • Compare device patch levels against Google and OEM guidance for CVE-2018-9378.
  • Review MDM compliance reports for devices missing relevant security updates.
  • Document exceptions where vendor fix availability is unclear or unsupported.
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-908: 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-9378 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
Medium
CVSS
6.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/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
6.2CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N2.53.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.2Medium
CVSS 3.1 vector shape for CVE-2018-9378Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/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
GoogleAndroidAndroid Kernelunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-908 · source CWE mapping

Use of Uninitialized Resource

Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.