LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9346: In BnAudioPolicyService::onTransact of AudioPolicyService.cpp, there is a possible information disclosure d...

In BnAudioPolicyService::onTransact of AudioPolicyService.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 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Android flaw can expose sensitive local data because part of the audio policy service may return uninitialized memory. It requires local access with low privileges and no user interaction. The main business concern is legacy or unmanaged Android devices that remain on affected versions without the relevant vendor security update.

Executive priority

Treat this as a moderate legacy-device risk. It is not evidenced as actively exploited, but affected Android versions are old and may signal broader patch hygiene problems. Prioritize inventory, patch verification, and replacement planning for devices that cannot be updated.

Technical view

CVE-2018-9346 is an information disclosure issue in BnAudioPolicyService::onTransact in AudioPolicyService.cpp, attributed to uninitialized data. CVSS 3.1 is 5.5: local attack vector, low complexity, low privileges, no user interaction, high confidentiality impact, and no integrity or availability impact.

Likely exposure

Exposure is most likely on Android 6, 6.0.1, 7, 8, 8.1, and listed NYC development branches. Other versions are not identified as affected in the supplied record. Risk is concentrated in legacy Android fleets, unmanaged personal devices, kiosks, and embedded Android deployments.

Exploitation context

The supplied sources do not show active exploitation, and the CVE is not listed as KEV. Exploitation is described as local, requiring low privileges but no user interaction. The practical impact is confidentiality loss rather than system compromise, data modification, or service outage.

Researcher notes

The record identifies CWE-908 and a local information disclosure path in Android AudioPolicyService. The supplied evidence does not include exploit details, proof-of-concept status, or product-specific OEM patch mappings. Validation should stay focused on affected-version exposure and vendor bulletin correlation.

Mitigation direction

  • Review the Android June 2018 security bulletin and relevant OEM guidance.
  • Apply vendor-provided Android security updates that address CVE-2018-9346.
  • Prioritize unsupported or unmanaged devices running listed affected Android versions.
  • Replace devices that cannot receive applicable vendor security updates.

Validation and detection

  • Inventory Android devices by OS version and security patch level.
  • Identify devices running the affected versions listed in the CVE record.
  • Confirm OEM advisories or build notes reference the applicable Android June 2018 fixes.
  • Track remediation evidence in MDM, asset, or vulnerability management records.
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-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-9346 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
5.5 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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
GoogleAndroid6, 6.0.1, 7, 8, 8.1, 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-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.