# CVE-2015-7505: Memory corruption in Libnsgif

> A stack-based buffer overflow in Libnsgif allows attackers to cause a crash or execute arbitrary code via a crafted GIF file.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-7505, GHSA-6vr7-cx9r-8cjr

## What is CVE-2015-7505?

CVE-2015-7505 is a high-severity memory corruption vulnerability in Libnsgif, published on 18 Feb 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Stack-based buffer overflow in the gif_next_LZW function in libnsgif.c in Libnsgif 0.1.2 allows context-dependent attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted LZW stream in a GIF file.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Netsurf-Browser Libnsgif.

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

Upgrade to a fixed version.

## Is CVE-2015-7505 being exploited?

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

## Other vulnerabilities in Libnsgif

- [CVE-2015-7506](https://insights.sbomify.com/CVE-2015-7506/): Denial of service in Libnsgif (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-7505 is a high-severity memory corruption vulnerability in Libnsgif, published on 18 Feb 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-7505 in the wild and no public exploit code.

Affected product: Libnsgif. 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-7505/ (Markdown: https://insights.sbomify.com/CVE-2015-7505/index.md)
```

## Sources

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

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