Skip to content
Privilege escalation checks for Linux systemd.
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
tests Update Feb 1, 2019
LICENSE put in a check to catch non-systemd systems Feb 15, 2019


Privilege escalation checks for Linux systemd.

This tool checks for issues on Linux systems that may lead to privilege escalation. The core focus in on systemd configuration.

This tool is under active development and is still at a very early stage. So far it does the following:

  • Basic sudo checks (nothing new and exciting here)
  • Checks for systemd paths that may be writeable (fat chance)
  • Checks for writable service, timer, and socket units (blah)
  • Disassembles these unit files and looks inside them for (EXCITING):
    • References to executables that are writable
    • References to broken symlinks pointing to writeable directories
    • Relative path statements
    • Unix socket files that are writeable (sneaky APIs)

This disassembly and analysis of unit files is what makes this tool unique. For general purpose privesc, the classic tools are far superior.

Future improvements may include things like:

  • Socket configuration issues
  • .conf file analysis


All functionality is contained in a single file, because installing packages in restricted shells is a pain. Written for Python2, as unfortunately we get stuck on on crap boxes without modern versions.

There is nothing to install, just grab the script and run it.

usage: [-h] [-n] [-d]

PrivEsc for modern Linux systemd, by initstring (

optional arguments:
  -h, --help       show this help message and exit
  -n, --nologging  do not write the output to a logfile
  -d, --debug      print some extra debugging info to the console


For testing purposes, you can run the tests/ script, which will create many vulnerable configuration issues on your system that uptux can identify. Running tests/ will undo these changes, but don't hold me to it. Needless to say, this is dangerous.

Use a VM for testing this way.

You can’t perform that action at this time.