CVE-2014-7951: n/a vulnerability

CVE-2014-7951: Directory traversal vulnerability in the Android debug bridge (aka adb) in Android 4.0.4 allows physically...

Directory traversal vulnerability in the Android debug bridge (aka adb) in Android 4.0.4 allows physically proximate attackers with a direct connection to the target Android device to write to arbitrary files owned by system via a .. (dot dot) in the tar archive headers.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 13:03 UTC (UTC+00:00)

Security readout for executives and security teams

This is an old Android adb weakness where someone with physical access to an Android 4.0.4 device could abuse backup archive paths to overwrite files owned by the system. It is not a typical internet-exposed server issue, but it matters for legacy phones, kiosks, lab devices, or embedded Android deployments. Exposure is most likely limited to legacy Android 4.0.4 devices where an attacker can physically connect to the device and interact with adb-related backup behavior. Modern supported Android builds are not identified as affected in the provided sources. Treat this as a legacy-device risk, not an internet-wide emergency. Priority rises if the organization still uses Android 4.0.4 devices in physical locations where attackers, visitors, contractors, or untrusted users can connect over USB. Mitigation focus: Inventory Android 4.0.4 devices and prioritize retirement or isolation.; Update affected devices to a vendor-supported build containing the AOSP fix.; Disable adb or USB debugging where operationally unnecessary..

Prepared: Jun 6, 2026, 02:28 UTC (UTC+00:00)

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.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2014-7951 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: Feb 20, 2020, 15:34 UTC (UTC+00:00)

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

3Source links

CVSS and timeline data

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

Source materials

CVE List V5 sourceCVE List V5
https://www.exploit-db.com/exploits/36813/CVE reference · x_refsource_MISC
https://android.googlesource.com/platform/frameworks/base/+/7bc601d%5E%21/#F0CVE reference · x_refsource_MISC

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

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