LiveActive security incident?Get immediate response
CVE Record

CVE-2014-7920: mediaserver in Android 2.2 through 5.x before 5.1 allows attackers to gain privileges.

mediaserver in Android 2.2 through 5.x before 5.1 allows attackers to gain privileges. NOTE: This is a different vulnerability than CVE-2014-7921.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2014-7920 is an old Android mediaserver privilege escalation issue. Devices running Android 2.2 through pre-5.1 5.x builds may allow an attacker to gain higher privileges. Business risk is concentrated in legacy Android phones, tablets, kiosks, or embedded deployments that were never upgraded.

Executive priority

Treat this as a legacy-risk cleanup item with high impact where exposed. It should not disrupt modern Android operations, but any remaining pre-5.1 Android devices deserve prompt review, isolation, or retirement.

Technical view

The CVE record identifies mediaserver in Android 2.2 through 5.x before 5.1 as vulnerable to privilege escalation. The public references include a Bits Please write-up and an Android frameworks/av code change. The provided sources do not include CVSS, CWE, affected CPEs, or detailed vendor remediation guidance beyond the pre-5.1 affected boundary.

Likely exposure

Exposure is likely limited to devices still running Android versions from 2.2 through 5.x before 5.1. Modern managed fleets are unlikely to be affected unless they include old, unsupported Android endpoints or Android-based appliances.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Public discussion exists, but this assessment should not treat exploitation as active without additional evidence. The issue matters because privilege escalation can turn a foothold into broader device compromise.

Researcher notes

Evidence is sparse in the CVE metadata: no CVSS, CWE, CPEs, or formal advisory text are provided. The strongest anchors are the CVE description, the public research reference, and the Android frameworks/av commit. Avoid assuming broader product impact without device firmware evidence.

Mitigation direction

  • Identify Android devices running versions before 5.1.
  • Upgrade affected devices to Android 5.1 or later where supported.
  • Retire or isolate devices that cannot receive supported updates.
  • Review OEM or platform vendor guidance for device-specific fixes.
  • Limit sensitive access from legacy Android endpoints.

Validation and detection

  • Inventory Android OS versions across managed and unmanaged device fleets.
  • Flag Android 2.2 through pre-5.1 5.x devices as potentially affected.
  • Check whether OEM firmware includes the referenced frameworks/av fix.
  • Confirm unsupported devices are isolated, replaced, or removed from sensitive workflows.
  • Document exceptions with compensating controls and retirement dates.
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.

cve · low confidence lookup

CVE-2014-7920 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
3Source links

CVSS and timeline data

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

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.