# CVE-2015-2785: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via a crafted recording file processed by the Byzanz playback command.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-2785, GHSA-6783-fxr3-9p6m, UBUNTU-CVE-2015-2785

## What is CVE-2015-2785?

CVE-2015-2785 is a high-severity memory corruption vulnerability in n/a, published on 29 Mar 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The GIF encoder in Byzanz allows remote attackers to cause a denial of service (out-of-bounds heap write and crash) or possibly execute arbitrary code via a crafted Byzanz debug data recording (ByzanzRecording file) to the byzanz-playback command.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Gnome Byzanz.

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

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

## Is CVE-2015-2785 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2785 is a high-severity memory corruption vulnerability in n/a, published on 29 Mar 2015. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-2785 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-2785/ (Markdown: https://insights.sbomify.com/CVE-2015-2785/index.md)
```

## Sources

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

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