# CVE-2015-8051: Other in n/a

> Adobe Premiere Clip for iOS mishandles unspecified input, potentially allowing attackers to exploit the application through unknown vectors.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 18 Nov 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3rfx-p4vj-g7v6

## What is CVE-2015-8051?

CVE-2015-8051 is a critical vulnerability in n/a, published on 18 Nov 2015. 

### Official description

The Adobe Premiere Clip app before 1.2.1 for iOS mishandles unspecified input, which has unknown impact and attack vectors.

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

It affects 1 product.


Products: Adobe Premiere Clip.

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

Upgrade to a fixed version.

## Is CVE-2015-8051 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-8051 is a critical vulnerability in n/a, published on 18 Nov 2015. 
Exploitation: There is no known exploitation of CVE-2015-8051 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-8051/ (Markdown: https://insights.sbomify.com/CVE-2015-8051/index.md)
```

## Sources

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

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