358
Root access vulnerability in glibc library impacts many Linux distros (securityaffairs.com)
submitted 2 years ago by to c/linux@lemmy.ml
79 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 158 points 2 years ago (5 children)

For your convenience:

The researchers pointed out that the vulnerability cannot be exploited remotely. An attacker can trigger the issue by providing crafted inputs to applications that employ these [syslog] logging functions [in apps that allow the user to feed crafted data to those functions].

This is a privilege escalation.

  • permalink
  • fedilink
  • source
  • hideshow 5 child comments
    •
  • [–] 4 points 2 years ago (2 children)

    This may be difficult to exploit in practice - I don't think most user applications use syslog.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    Unless you have user access to a system with gcc on it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 9 points 2 years ago

    You still need some privileged process to exploit. Glibc code doesn't get any higher privileges than the rest of the process. From kernel's point of view, it's just a part of the program like any other code.

    So if triggering the bug in your own process was enough for privilege escalation, it would also be a critical security vulnerability in the kernel - it can't allow you to execute a magic sequence of instructions in your process and become a root, that completely destroys any semblance of process / user isolation.

  • permalink
  • fedilink
  • source
  • parent