Potential Privilege Escalation via Recently Compiled Executable
This rule monitors a sequence involving a program compilation event followed by its execution and a subsequent alteration of UID permissions to root privileges. This behavior can potentially indicate the execution of a kernel or software privilege escalation exploit.
Elastic rule (View on GitHub)
1[metadata]
2creation_date = "2023/08/28"
3integration = ["endpoint"]
4maturity = "production"
5updated_date = "2024/05/21"
6
7[rule]
8author = ["Elastic"]
9description = """
10This rule monitors a sequence involving a program compilation event followed by its execution and a subsequent
11alteration of UID permissions to root privileges. This behavior can potentially indicate the execution of a kernel or
12software privilege escalation exploit.
13"""
14from = "now-9m"
15index = ["logs-endpoint.events.*"]
16language = "eql"
17license = "Elastic License v2"
18name = "Potential Privilege Escalation via Recently Compiled Executable"
19risk_score = 47
20rule_id = "193549e8-bb9e-466a-a7f9-7e783f5cb5a6"
21setup = """## Setup
22
23This rule requires data coming in from Elastic Defend.
24
25### Elastic Defend Integration Setup
26Elastic Defend is integrated into the Elastic Agent using Fleet. Upon configuration, the integration allows the Elastic Agent to monitor events on your host and send data to the Elastic Security app.
27
28#### Prerequisite Requirements:
29- Fleet is required for Elastic Defend.
30- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
31
32#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
33- Go to the Kibana home page and click "Add integrations".
34- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
35- Click "Add Elastic Defend".
36- Configure the integration name and optionally add a description.
37- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
38- Select a configuration preset. Each preset comes with different default settings for Elastic Agent, you can further customize these later by configuring the Elastic Defend integration policy. [Helper guide](https://www.elastic.co/guide/en/security/current/configure-endpoint-integration-policy.html).
39- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
40- Enter a name for the agent policy in "New agent policy name". If other agent policies already exist, you can click the "Existing hosts" tab and select an existing policy instead.
41For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
42- Click "Save and Continue".
43- To complete the integration, select "Add Elastic Agent to your hosts" and continue to the next section to install the Elastic Agent on your hosts.
44For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
45"""
46severity = "medium"
47tags = [
48 "Domain: Endpoint",
49 "OS: Linux",
50 "Use Case: Threat Detection",
51 "Tactic: Privilege Escalation",
52 "Use Case: Vulnerability",
53 "Data Source: Elastic Defend",
54]
55type = "eql"
56
57query = '''
58sequence by host.id with maxspan=1m
59 [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
60 process.name in ("gcc", "g++", "cc") and user.id != "0"] by process.args
61 [file where host.os.type == "linux" and event.action == "creation" and event.type == "creation" and
62 process.name == "ld" and user.id != "0"] by file.name
63 [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
64 user.id != "0"] by process.name
65 [process where host.os.type == "linux" and event.action in ("uid_change", "guid_change") and event.type == "change" and
66 user.id == "0"] by process.name
67'''
68
69
70[[rule.threat]]
71framework = "MITRE ATT&CK"
72[[rule.threat.technique]]
73id = "T1068"
74name = "Exploitation for Privilege Escalation"
75reference = "https://attack.mitre.org/techniques/T1068/"
76
77
78[rule.threat.tactic]
79id = "TA0004"
80name = "Privilege Escalation"
81reference = "https://attack.mitre.org/tactics/TA0004/"
Related rules
- Potential Privilege Escalation via CVE-2023-4911
- Potential Privilege Escalation via OverlayFS
- Potential Privilege Escalation via PKEXEC
- Potential Sudo Privilege Escalation via CVE-2019-14287
- Sudo Heap-Based Buffer Overflow Attempt