# CVE-2018-1000532: Path traversal in n/a

> A local unprivileged user can inhibit execution of arbitrary programs by other users via the beep utility's device option, causing denial of service.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 26 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-1000532, GHSA-pg7q-39qh-p6jg, UBUNTU-CVE-2018-1000532

## What is CVE-2018-1000532?

CVE-2018-1000532 is a medium-severity path traversal vulnerability in n/a, published on 26 Jun 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

beep version 1.3 and up contains a External Control of File Name or Path vulnerability in --device option that can result in Local unprivileged user can inhibit execution of arbitrary programs by other users, allowing DoS. This attack appear to be exploitable via The system must allow local users to run beep.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Beep Project Beep.

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

Apply the vendor's patch.

## Is CVE-2018-1000532 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-0492](https://insights.sbomify.com/CVE-2018-0492/): Race condition in beep (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1000532 is a medium-severity path traversal vulnerability in n/a, published on 26 Jun 2018. 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-2018-1000532 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-1000532/ (Markdown: https://insights.sbomify.com/CVE-2018-1000532/index.md)
```

## Sources

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

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