# CVE-2017-8933: Denial of service in n/a

> A local attacker can cause a denial of service by exploiting insecure temporary file usage in the menu cache library.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2017
- **Updated:** 16 Sep 2024
- **Also known as:** CVE-2017-7499, DEBIAN-CVE-2017-8933, GHSA-445v-p4f3-529c, MGASA-2017-0155, UBUNTU-CVE-2017-8933

## What is CVE-2017-8933?

CVE-2017-8933 is a low-severity denial of service vulnerability in n/a, published on 15 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Libmenu-cache 1.0.2 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (menu unavailability).

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2017-8933?

It affects 1 product.


Products: Libmenu-Cache Project Libmenu-Cache.

## How do I fix CVE-2017-8933?

Apply the vendor's patch.

## Is CVE-2017-8933 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8933 and fix it if it is affected.

What it is: CVE-2017-8933 is a low-severity denial of service vulnerability in n/a, published on 15 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-8933 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-2017-8933/ (Markdown: https://insights.sbomify.com/CVE-2017-8933/index.md)
```

## Sources

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

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