# CVE-2018-11657: Denial of service in n/a

> An attacker can cause a denial of service via an infinite loop in the MiniUPnP ngiflib library when processing malicious GIF images.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jun 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-mfwc-pxgh-fj85

## What is CVE-2018-11657?

CVE-2018-11657 is a high-severity denial of service vulnerability in n/a, published on 1 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ngiflib.c in MiniUPnP ngiflib 0.4 has an infinite loop in DecodeGifImg and LoadGif.

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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

It affects 1 product.


Products: Miniupnp Project Ngiflib.

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

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

## Is CVE-2018-11657 being exploited?

There is no known exploitation of CVE-2018-11657 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-11657 and fix it if it is affected.

What it is: CVE-2018-11657 is a high-severity denial of service vulnerability in n/a, published on 1 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-11657 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-11657/ (Markdown: https://insights.sbomify.com/CVE-2018-11657/index.md)
```

## Sources

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

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