News for hackers. Stuff that matters.

A comment on CVE-2017-16544: A Busybox autocompletion vulnerability. Parent comment

Re:CVE-2017-16544: A Busybox autocompletion vulnerability by jlgaddis on Monday November 20, 2017 @10:56AM (#15740780)
It could be good for me. We ($work) have some embedded devices running BusyBox that we only have limited (i.e. non-root) access to. I'm looking forward for a way to escalate privileges on these devices as a result of this!
[ Parent | on HN ]
Re:CVE-2017-16544: A Busybox autocompletion vulnerability by helper on Monday November 20, 2017 @12:31PM (#15741562)
How do you get privilege escalation from shell escape sequences?
[ Parent | on HN ]
Re:CVE-2017-16544: A Busybox autocompletion vulnerability by vetrom on Monday November 20, 2017 @04:57PM (#15743677)
It would be a stretch, but lets say you're driving some poorly thought out automation over a pty that has some sort of terminal emulator attached that has any sort of output-changeable answerback-like sequence.

The pty part is important because some software will assume you're running interactive if it sees that its STDIN/OUT is a pty, and change its functionality accordingly.

[ Parent | on HN ]
Re:CVE-2017-16544: A Busybox autocompletion vulnerability by jlgaddis on Monday November 20, 2017 @05:54PM (#15744107)
Crazier shit has happened. In my case, pretty much everything on these devices runs as root so it may very well be possible.
[ Parent | on HN ]