LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9405: In BnDmAgent::onTransact of dm_agent.cpp, there is a possible out of bounds write due to a missing bounds c...

In BnDmAgent::onTransact of dm_agent.cpp, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

MediumCVSS 6.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-9405 is an Android Kernel flaw in dm_agent.cpp that could let a local, already highly privileged actor corrupt memory and gain or misuse System-level privileges. No user interaction is required. The provided sources do not show internet-exposed attack paths or confirmed active exploitation.

Executive priority

Treat this as a moderate mobile platform risk. It is not shown as remotely exploitable or actively exploited, but successful abuse could have high device impact where vulnerable Android builds remain deployed.

Technical view

BnDmAgent::onTransact lacks a bounds check, creating a possible out-of-bounds write classified as CWE-787. The CVSS 3.1 vector is local, low complexity, high privileges required, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to Android device builds containing the affected Android Kernel dm_agent.cpp behavior and missing the relevant June 2018 Pixel/Android security update. The source bundle does not enumerate specific device models, OEM branches, or downstream kernel versions.

Exploitation context

The evidence supports local privilege escalation only. The CVSS vector requires high privileges, and KEV status is false. No cited source in the bundle states this CVE is exploited in the wild or provides public exploit availability.

Researcher notes

Key uncertainty is downstream exposure. The CVE identifies Android Kernel and BnDmAgent::onTransact, but the bundle does not list exact commits, affected OEM versions, or fixed build identifiers beyond the Pixel bulletin reference.

Mitigation direction

  • Apply vendor or OEM Android updates that cover CVE-2018-9405.
  • Review the June 2018 Pixel security bulletin for official remediation context.
  • Prioritize unsupported Android devices for replacement or isolation.
  • Restrict installation and execution of untrusted local privileged software.
  • Check Google or OEM guidance before assuming a backported fix exists.

Validation and detection

  • Inventory Android and Pixel devices in scope.
  • Verify each device has a vendor update covering CVE-2018-9405.
  • Confirm security patch reporting through MDM or endpoint inventory.
  • Check whether custom Android builds include the affected dm_agent.cpp component.
  • Document devices without vendor support as residual risk.
Prepared
Confidence
medium
Sources
3

Public sources used

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-9405 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.7 (3.1)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.1 score

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroidAndroid Kernelunaffected
Weakness

CWE details

CWE-787

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.

Open CWE intelligenceSame-CWE CVEs