LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13238: In XBLRamDump mode, there is a debug feature that can be used to dump memory contents, if an attacker has p...

In XBLRamDump mode, there is a debug feature that can be used to dump memory contents, if an attacker has physical access to the device. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. Product: Android. Versions: Android kernel. Android ID: A-64610940.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This issue exposes memory contents through an Android kernel debug ramdump feature when someone has physical access to a device. The source does not indicate remote exploitation or active abuse. Business urgency depends on whether vulnerable Android devices remain in service and whether attackers could physically handle them. Exposure is most likely on older Android devices or device images that did not receive the February 2018 Android security bulletin fixes. The key condition is physical access to the device; ordinary internet-facing exposure is not supported by the supplied sources. Prioritize remediation for devices holding sensitive data, shared lab hardware, field devices, and unsupported Android fleets. This is not presented as remotely exploitable, but physical-access memory disclosure can still create confidentiality impact if affected devices are lost, seized, or mishandled. Mitigation focus: Apply vendor Android updates covering the February 2018 security bulletin.; Retire unsupported Android devices that cannot receive relevant security updates.; Limit physical access to managed devices and sensitive test hardware..

Prepared

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.

cve · low confidence lookup

CVE-2017-13238 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Google Inc.AndroidAndroid kernelListed
Weakness

CWE details

No CWE listed

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