LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This CVE describes a local denial-of-service issue in beep, tied to its --device option. If local users can run beep, an unprivileged user may be able to disrupt other users by blocking execution of selected programs. The provided record does not show remote impact, data theft, privilege escalation, or active exploitation.

Executive priority

Handle through normal vulnerability management unless beep is present on shared systems with untrusted local users. Business risk is mainly local disruption, not remote breach, based on the provided evidence. Prioritize inventory and restriction over emergency response.

Technical view

The source bundle identifies External Control of File Name or Path in beep version 1.3 and up, specifically through the --device option. The stated impact is local denial of service: an unprivileged user can inhibit execution of arbitrary programs by other users when local beep execution is allowed. CVSS, CWE, and normalized affected-product data are incomplete.

Likely exposure

Exposure is most plausible on shared Unix-like systems where beep is installed and executable by local users. Single-user systems, containers without beep, or environments where local users cannot run beep have lower apparent exposure. The bundle does not provide CPEs, distributions, package names, or fixed versions.

Exploitation context

The record says exploitation requires a system that allows local users to run beep. CISA KEV is false in the bundle, and no cited source in the bundle reports active exploitation. The issue should be assessed as local availability risk, not remote compromise, based on available evidence.

Researcher notes

Evidence is sparse. The CVE names beep 1.3 and up and the --device option, but the bundle lacks CVSS, CWE, CPEs, fixed versions, or detailed vendor remediation. Avoid broad product claims beyond beep and validate against the linked GitHub discussion and package-maintainer guidance.

Mitigation direction

  • Inventory systems where beep is installed and available to local users.
  • Restrict local execution of beep where it is not operationally required.
  • Check upstream or distribution package guidance for fixed versions or hardening advice.
  • Prioritize shared servers, jump hosts, lab systems, and multi-user workstations.
  • Document any accepted risk where beep remains available to untrusted users.

Validation and detection

  • Confirm whether beep is installed on in-scope systems.
  • Confirm whether non-admin local users can execute beep.
  • Review package metadata for version and vendor patch status.
  • Check local policy for multi-user access to affected hosts.
  • Monitor vendor or distribution advisories for updated remediation guidance.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2018-1000532 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.