LiveActive security incident?Get immediate response
CVE Record

CVE-2015-2001: The MetaIO SDK before 6.0.2.1 for Android might allow attackers to execute arbitrary code by leveraging a f...

The MetaIO SDK before 6.0.2.1 for Android might allow attackers to execute arbitrary code by leveraging a finalize method in a Serializable class that improperly passes an attacker-controlled pointer to a native function.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE affects Android apps that embedded MetaIO SDK versions before 6.0.2.1. The flaw could let attacker-controlled data reach native code through object cleanup logic, potentially causing arbitrary code execution. The public bundle does not identify affected downstream apps or active exploitation.

Executive priority

Prioritize investigation if your organization still maintains older Android apps using augmented reality or MetaIO components. Business urgency is conditional: the impact could be severe, but the provided evidence does not show active exploitation or named affected products.

Technical view

The issue is in a Serializable class finalize method in MetaIO SDK for Android before 6.0.2.1. It improperly passes an attacker-controlled pointer to a native function, creating a possible arbitrary code execution condition. No CVSS, CWE, or detailed affected CPE data is provided.

Likely exposure

Exposure is most likely in legacy Android applications that package MetaIO SDK before 6.0.2.1. The source bundle does not name specific vendors, apps, package names, or deployment patterns, so confirmation requires software composition review of Android builds and dependencies.

Exploitation context

The CVE is not listed as KEV in the provided data, and the bundle provides no evidence of active exploitation. Public references are a USENIX WOOT 2015 paper and Aleph Security advisory. Treat exploit status as unconfirmed.

Researcher notes

Key evidence gaps are missing CVSS, CWE, CPEs, downstream app list, and exploit telemetry. The version boundary is the strongest remediation clue: MetaIO SDK before 6.0.2.1 for Android is described as affected.

Mitigation direction

  • Inventory Android applications for bundled MetaIO SDK components.
  • Upgrade MetaIO SDK to 6.0.2.1 or later where present.
  • Remove unused or unsupported MetaIO SDK code from legacy apps.
  • Check original vendor or maintainer guidance before release decisions.
  • Prioritize apps handling untrusted files, intents, or serialized objects.

Validation and detection

  • Review Android dependency manifests and packaged libraries for MetaIO SDK.
  • Confirm exact SDK version in source, binaries, and build artifacts.
  • Map any exposed app paths that process untrusted serialized data.
  • Run regression tests after SDK upgrade or removal.
  • Document affected apps, version evidence, and remediation status.
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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-2015-2001 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.

Source materials

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.