LiveActive security incident?Get immediate response
CVE Record

CVE-2023-40110: In multiple functions of MtpPacket.cpp, there is a possible out of bounds write due to a heap buffer overflow.

In multiple functions of MtpPacket.cpp, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

MediumCVSS 6.2Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-40110 is a heap buffer overflow in Android’s MtpPacket.cpp handling. The reported impact is local privilege escalation: a person or app with local access could potentially gain higher privileges. The bundle does not cite active exploitation. Business urgency is moderate, focused on ensuring Android devices have received the November 2023 Android security update or equivalent vendor patch.

Executive priority

Treat as a moderate mobile endpoint hygiene issue. It is not cited as actively exploited, but it can raise local privileges on affected Android devices. Prioritize patch compliance for managed and BYOD Android fleets.

Technical view

Multiple functions in Android frameworks/av MtpPacket.cpp may perform an out-of-bounds heap write. The CVE maps to CWE-787 and affects Android 11, 12, 12L, 13, and 14. Reported CVSS is 6.2. The description says user interaction is needed, while the supplied CVSS vector lists UI:N; treat that detail as inconsistent.

Likely exposure

Exposure is likely limited to unpatched Android 11 through 14 devices, including 12L, where the vulnerable MTP component is present. Risk depends on device security patch level and OEM backport status.

Exploitation context

Sources describe local escalation of privilege with no additional execution privileges needed. The bundle does not state public exploitation or inclusion in CISA KEV. Exploitation requirements are somewhat unclear because user interaction evidence conflicts across supplied metadata.

Researcher notes

Primary evidence is Android bulletin metadata and a frameworks/av source change. The source bundle does not provide exploit detail, affected OEM models, or standalone mitigations beyond patching. Note the inconsistency between the description’s user-interaction statement and the supplied CVSS UI:N vector.

Mitigation direction

  • Apply the Android Security Bulletin 2023-11-01 update or later vendor equivalent.
  • Confirm OEM security patches cover CVE-2023-40110 for managed devices.
  • Prioritize unsupported or delayed-update Android devices for replacement or isolation.
  • Check vendor guidance where patch availability is unclear.

Validation and detection

  • Inventory Android devices running versions 11, 12, 12L, 13, or 14.
  • Verify each device reports a November 2023 or later Android security patch level.
  • Check OEM advisories for explicit CVE-2023-40110 coverage.
  • Review MDM compliance reports for devices blocked from updates.
Prepared
Confidence
medium
Sources
4

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-2023-40110 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
3Source 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-2023-40110Attack 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
GoogleAndroid14, 13, 12L, 12, 11unaffected
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.