# CVE-2018-10717: Memory corruption in n/a

> Remote attackers can cause denial of service or potential code execution via a crafted GIF file due to a heap-based buffer overflow in the ngiflib library.

- **Severity:** High 8.8 (`CVSS:3.0/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:** No
- **Published:** 3 May 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7fxx-c4v5-3v6v

## What is CVE-2018-10717?

CVE-2018-10717 is a high-severity memory corruption vulnerability in n/a, published on 3 May 2018. 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

The DecodeGifImg function in ngiflib.c in MiniUPnP ngiflib 0.4 does not consider the bounds of the pixels data structure, which allows remote attackers to cause a denial of service (WritePixels heap-based buffer overflow and application crash) or possibly have unspecified other impact via a crafted GIF file, a different vulnerability than CVE-2018-10677.

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

## Which versions are affected by CVE-2018-10717?

It affects 1 product.


Products: Miniupnp Project Ngiflib.

## How do I fix CVE-2018-10717?

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

## Is CVE-2018-10717 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11575](https://insights.sbomify.com/CVE-2018-11575/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-11576](https://insights.sbomify.com/CVE-2018-11576/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-36530](https://insights.sbomify.com/CVE-2021-36530/): Memory corruption in n/a (high 8.8)
- [CVE-2021-36531](https://insights.sbomify.com/CVE-2021-36531/): Memory corruption in n/a (high 8.8)
- [CVE-2019-20219](https://insights.sbomify.com/CVE-2019-20219/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10717 and fix it if it is affected.

What it is: CVE-2018-10717 is a high-severity memory corruption vulnerability in n/a, published on 3 May 2018. 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-2018-10717 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-2018-10717/ (Markdown: https://insights.sbomify.com/CVE-2018-10717/index.md)
```

## Sources

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

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