Server Message Block (SMB) can be used to make file systems and resources available to other systems in network environments.
This ability mounts a remote network share and copies an agent file to that directory on the remote system.
A problem in the way sudo implemented executing commands with arbitrary user IDs was discovered. If a sudoers item is created to let the attacker to perform a command as any user other than root, the attacker can use this issue to circumvent that restriction.
In this TTP we exploit this vulnerability to run an elevated Pneuma instance.
A named pipe is a named, one-way or duplex pipe for communication between the pipe server and one or more pipe clients.
Named pipes can be used to provide communication between processes on the same computer or between processes on
different computers across a network. This procedure uses PowerSploit to conduct a named-pipe impersonation.
In privileged mode, Kubernetes pods can mount the host filesystem and may be subject to container escape. This chain attempts to mount the host filesystem to test whether the host is vulnerable to a container escape. It is critical that pods are not able to mount the host filesystem, as attackers may create persistence by altering mounted files, elevating privileges, and escaping the container.
The docker.sock UNIX socket is used by the Docker daemon for the acessing the Docker API. This TTP determines if a Docker socket escape via docker.sock is possible. An attacker may be able to escape the container if the Docker socket is mounted in it.
Spawn a beacon using the (Sequoia) identified in CVE-2021-3156. fs/seq_file.c in the Linux kernel 3.16 through 5.13.x before 5.13.4 does not properly restrict seq buffer allocations, leading to an integer overflow, an Out-of-bounds Write, and escalation to root by an unprivileged user, aka CID-8cae8cd89f05. You need 1 million free inodes available in the directory where you execute the exploit payload. Using the home directory yields highest probability of success.
Utilizing Docker via unprotected tcp socket (2375/tcp, maybe 2376/tcp with tls but without tls-auth), an attacker can create a docker container with the '/' path mounted with read/write permissions on the host server that is running the docker container and use chroot to escape the container-jail. This TTP mounts the hosts root directory inside the container's /mnt directory and runs schism as root on the host machine.
Used to reset Windows Store settings according to its manifest file. Modify the default registry value at
HKCU\Software\Classes\AppX82a6gwre4fdg3bt635tn5ctqjf8msdd2\Shell\open\command to run something elevated.
During startup, eventvwr.exe checks the registry value HKCU\Software\Classes\mscfile\shell\open\command for the location
of mmc.exe, which is used to open the eventvwr.msc saved console file. If the location of another binary or script is
added to this registry value, it will be executed as a high-integrity process without a UAC prompt being displayed to
the user.
If the current user context has write permissions to the docker.sock unix socket file, we are able to take complete ownership
of all dockers running on the system and perform arbitrary docker daemon/CLI commands against all containers. This is accomplished
by creating a new docker container, passing in the docker.sock file descriptor, then installing dockerd inside the container. From
there we can run docker commands in any container.
Containers that can mount the host filesystem may be vulnerable to a container escape. This TTP attempts to mount the host filesystem and identify a root directory. It is important that containers cannot mount the host filesystem, as adversaries may establish persistence by modifying mounted files, elevate privileges, and escape the container.