Stories
Slash Boxes
Comments

SoylentNews is people

posted by janrinok on Tuesday April 10 2018, @01:47AM   Printer-friendly
from the who's-a-fool-now? dept.

One of the silliest bugs on record emerged late last week, when Debian project leader Chris Lamb took to the distro's security to post an advisory that the little [beep] utility had a local privilege escalation vulnerability.

The utility lets either a command line user control a PC's speaker, or – more usefully – a program can pipe the command out to the command line to tell the user something's happened. If, of course, their machines still have a beeper-speaker, which is increasingly rare and raises the question why the utility still exists. Since beep isn't even installed by default, it's not hard to see the issue would have gone un-noticed.

News of the bug emerged at holeybeep.ninja/, a site that combines news of the bug with attempts at satirising those who brand bugs and put up websites about them.

But the joke's on holeybeep.ninja because according to the discussion at the Debian mailing list, the fix the site provided didn't fix all of beep's problems. As Tony Hoyle wrote: “The patch vulnerability seems more severe to me, as people apply patches all the time (they shouldn't do it as root, but people are people) … It's concerning that the holeybeep.ninja site exploited an unrelated fault for 'fun' without apparently telling anyone.”

German security researcher and journalist Hanno Böck alerted the OSS-sec list to further issues on Sunday.

[...] Böck's note also linked to an integer overflow and a bug in the patch supposed to fix the original issue.

As a result, Böck wrote, beep should probably be discarded: it needs a proper code review, and there's no much point to the effort “for a tool talking to the PC speaker, which doesn't exist in most modern systems anyway.


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by Arik on Tuesday April 10 2018, @02:49AM (2 children)

    by Arik (4543) on Tuesday April 10 2018, @02:49AM (#664790) Journal
    I hate to say metoo, but metoo man, metoo.

    Beep is one of the most useful packages in the distro. I didn't read the article yet but just based on the last line of the summary here this Böck has clearly risen to his level of utter incompetence, just as Peter predicted.
    --
    If laughter is the best medicine, who are the best doctors?
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2  
  • (Score: 2) by TheRaven on Tuesday April 10 2018, @03:55PM (1 child)

    by TheRaven (270) on Tuesday April 10 2018, @03:55PM (#664992) Journal
    The only reason that any of these issues are a problem is that people are installing beep setuid root. A sane install grants /dev/dsp (or whatever the relevant device is) permissions to anyone any needs to be able to make sound and then beep can simply use this permission. With SELinux (or the FreeBSD MAC framework, or equivalent), it's possible to grant access to the device to the program, rather than a user, so any user running beep could go beep but not access anything as root.
    --
    sudo mod me up
    • (Score: 2) by Arik on Tuesday April 10 2018, @04:57PM

      by Arik (4543) on Tuesday April 10 2018, @04:57PM (#665019) Journal
      "The only reason that any of these issues are a problem is that people are installing beep setuid root."

      Seriously?

      :facedesk:
      --
      If laughter is the best medicine, who are the best doctors?