beep vulnerabilities and fixes
Recent CVEs affecting beep, with upgrade or downgrade steps. 2 tracked.
beep has 2 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 1. Most recent: 2018-06-26. Highest priority: CVE-2018-0492 (score 53/100).
- CVE-2018-1000532 MEDIUM 4.7 DOWNGRADE beep version 1.3 and up contains a External Control of File Name or Path vulnerability in --device option that
- 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
FAQ
How do I fix beep vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is beep being exploited right now?
None of the tracked beep CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which beep CVE should I patch first?
CVE-2018-0492 currently ranks highest (53/100): Johnathan Nightingale beep through 1.3.4, if setuid, has a race condition that allows local privilege escalati.