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

> A stack-based buffer overflow in uWSGI allows attackers to execute arbitrary code or cause a denial of service via a large directory length.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 6 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2018-6758, DEBIAN-CVE-2018-6758, DLA-1275-1, GHSA-gp37-5368-2566, UBUNTU-CVE-2018-6758, openSUSE-SU-2024:11490-1

## What is CVE-2018-6758?

CVE-2018-6758 is a critical memory corruption vulnerability in n/a, published on 6 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The uwsgi_expand_path function in core/utils.c in Unbit uWSGI through 2.0.15 has a stack-based buffer overflow via a large directory length.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `uwsgi` | openSUSE:Tumbleweed | All versions | 2.0.19.1-3.10 |

Products: Unbit Uwsgi.

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

Apply the vendor's patch.

## Is CVE-2018-6758 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6758 is a critical memory corruption vulnerability in n/a, published on 6 Feb 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-6758 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-6758/ (Markdown: https://insights.sbomify.com/CVE-2018-6758/index.md)
```

## Sources

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

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