t1543-002-systemd-service

name	T1543.002_systemd-service
description	Adversaries may create or modify systemd services to repeatedly execute malicious payloads as part of persistence.
category	configuration
version	18.1
author	cyberstrike-official
tags	["mitre-attack","enterprise","t1543.002","persistence","privilege-escalation","linux","sub-technique"]
technique_id	T1543.002
tactic	persistence
all_tactics	["persistence","privilege-escalation"]
platforms	["Linux"]
mitre_url	https://attack.mitre.org/techniques/T1543/002
tech_stack	["linux"]
cwe_ids	["CWE-276"]
chains_with	["T1543","T1543.001","T1543.003","T1543.004","T1543.005"]
prerequisites	["T1543"]
severity_boost	{"T1543":"Chain with T1543 for deeper attack path","T1543.001":"Chain with T1543.001 for deeper attack path","T1543.003":"Chain with T1543.003 for deeper attack path"}

T1543.002 Systemd Service

Sub-technique of: T1543

High-Level Description

Adversaries may create or modify systemd services to repeatedly execute malicious payloads as part of persistence. Systemd is a system and service manager commonly used for managing background daemon processes (also known as services) and other system resources. Systemd is the default initialization (init) system on many Linux distributions replacing legacy init systems, including SysVinit and Upstart, while remaining backwards compatible.

Systemd utilizes unit configuration files with the .service file extension to encode information about a service's process. By default, system level unit files are stored in the /systemd/system directory of the root owned directories (/). User level unit files are stored in the /systemd/user directories of the user owned directories ($HOME).

Inside the .service unit files, the following directives are used to execute commands:

• ExecStart, ExecStartPre, and ExecStartPost directives execute when a service is started manually by systemctl or on system start if the service is set to automatically start.
• ExecReload directive executes when a service restarts.
• ExecStop, ExecStopPre, and ExecStopPost directives execute when a service is stopped.

Adversaries have created new service files, altered the commands a .service file’s directive executes, and modified the user directive a .service file executes as, which could result in privilege escalation. Adversaries may also place symbolic links in these directories, enabling systemd to find these payloads regardless of where they reside on the filesystem.

The .service file’s User directive can be used to run service as a specific user, which could result in privilege escalation based on specific user/group permissions.

Systemd services can be created via systemd generators, which support the dynamic generation of unit files. Systemd generators are small executables that run during boot or configuration reloads to dynamically create or modify systemd unit files by converting non-native configurations into services, symlinks, or drop-ins (i.e., Boot or Logon Initialization Scripts).

Kill Chain Phase

• Persistence (TA0003)
• Privilege Escalation (TA0004)