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

> A crafted file causes GPP to exhaust stack memory, leading to a segmentation fault and denial of service.

- **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:** Yes
- **Published:** 16 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-17076, GHSA-gw2g-5r47-23jh, UBUNTU-CVE-2018-17076, openSUSE-SU-2024:13313-1

## What is CVE-2018-17076?

CVE-2018-17076 is a high-severity denial of service vulnerability in n/a, published on 16 Sep 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

GPP through 2.25 will try to use more memory space than is available on the stack, leading to a segmentation fault or possibly unspecified other impact via a crafted file.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gpp` | openSUSE:Tumbleweed | All versions | 2.28-1.1 |

Products: Logological General-Purpose Preprocessor.

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

Upgrade to a fixed version.

## Is CVE-2018-17076 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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