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

> Remote attackers can cause a denial of service via a corrupt AFF image in the AFFLIB library, requiring a patch to mitigate.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 11 Mar 2018
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-8050, GHSA-ww5j-x7v8-wc43, MGASA-2018-0231, UBUNTU-CVE-2018-8050, USN-6518-1

## What is CVE-2018-8050?

CVE-2018-8050 is a medium-severity denial of service vulnerability in n/a, published on 11 Mar 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 af_get_page() function in lib/afflib_pages.cpp in AFFLIB (aka AFFLIBv3) through 3.7.16 allows remote attackers to cause a denial of service (segmentation fault) via a corrupt AFF image that triggers an unexpected pagesize value.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Afflib Project Afflib.

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

Apply the vendor's patch.

## Is CVE-2018-8050 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8050 is a medium-severity denial of service vulnerability in n/a, published on 11 Mar 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-8050 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-8050/ (Markdown: https://insights.sbomify.com/CVE-2018-8050/index.md)
```

## Sources

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

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