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

Routine

MEDIUM 4.7DOWNGRADE

CVE-2018-1000532 is a medium-severity flaw (CVSS 4.7) affecting beep. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.7 (Medium)
Attack vector	Local
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 72%)
CISA exploited list	No
Weakness	CWE-22
Published	2018-06-26
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: beep project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-06-26 16:29 UTCPublished CVE record published
2026-06-17 01:32 UTCUpdated Record last modified

beep project beep DOWNGRADE

Affected: 1.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.3

1. Check installed version

apt-cache policy beep || rpm -q beep || beep --version

2. No fixed release: DOWNGRADE to a release before 1.3 (Debian / Ubuntu)

apt-cache madison beep sudo apt install beep=<VERSION_BEFORE_1.3> sudo apt-mark hold beep

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list beep sudo dnf downgrade beep-<VERSION_BEFORE_1.3> sudo dnf versionlock add beep

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-1000532?

beep: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2018-1000532 being exploited?

CVE-2018-1000532 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-1000532 affect?

CVE-2018-1000532 affects beep. Severity is medium (CVSS 4.7). 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 appea

How urgent is CVE-2018-1000532?

Priority 23/100. No elevated risk signals yet.

Related CVEs

CVE-2018-0492 HIGH 7.0 UPGRADE MITIGATE Johnathan Nightingale beep through 1.3.4, if setuid, has a race condition that allows local privilege escalati

References

← Back to latest CVEs