CVE-2018-1000532 json
beep version 1.3 and up contains a External Control of File Name or Path vulnerability in --device option that can result in Local unprivil…
published 2018-06-26 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-1924
- cvss
- 4.7
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- beep Debian 14, Debian 13, Debian 12 1.4.3-1
debian advisories DEBIAN-CVE-2018-1000532
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2018-1000532 updated cvss 5.5
beep: External control of file name or path via --device option
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 4.7 | CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 1.9 | AV:L/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
github.com
/johnath/beep/issues/11#issuecomment-379514298
third-party-advisory
Sources
- CVE List CVE-2018-1000532
- NVD CVE-2018-1000532
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.