# CVE-2015-2001: 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


- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Mar 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-x2vq-qwv5-pqx3

## What is CVE-2015-2001?

CVE-2015-2001 is a critical vulnerability in n/a, published on 29 Mar 2018. 

### Official description

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.

Weakness: CWE-118 (Incorrect Access of Indexable Resource)

## Which versions are affected by CVE-2015-2001?

It affects 1 product.


Products: Metaio Metaio Sdk.

## How do I fix CVE-2015-2001?

No fix has been published for CVE-2015-2001 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-2001 being exploited?

There is no known exploitation of CVE-2015-2001 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2001 and fix it if it is affected.

What it is: CVE-2015-2001 is a critical vulnerability in n/a, published on 29 Mar 2018. 
Exploitation: There is no known exploitation of CVE-2015-2001 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-2001/ (Markdown: https://insights.sbomify.com/CVE-2015-2001/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-2001
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-2001
- OSV: https://osv.dev/vulnerability/CVE-2015-2001

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-2001/
Summaries are generated and may contain mistakes; the official description above is the record.