Potential Privilege Escalation via Enlightenment

 1[metadata]
 2creation_date = "2024/01/05"
 3integration = ["endpoint"]
 4maturity = "production"
 5updated_date = "2024/11/07"
 6
 7[rule]
 8author = ["Elastic"]
 9description = """
10Identifies an attempt to exploit a local privilege escalation CVE-2022-37706 via a flaw in Linux window manager package
11Enlightenment. enlightenment_sys in Enlightenment before 0.25.4 allows local users to gain privileges because it is
12setuid root, and the system library function mishandles pathnames that begin with a /dev/.. substring.
13"""
14from = "now-9m"
15index = ["logs-endpoint.events.*"]
16language = "eql"
17license = "Elastic License v2"
18name = "Potential Privilege Escalation via Enlightenment"
19references = ["https://ubuntu.com/security/CVE-2022-37706", "https://www.exploit-db.com/exploits/51180"]
20risk_score = 73
21rule_id = "bc0fc359-68db-421e-a435-348ced7a7f92"
22setup = """## Setup
23
24
25This rule requires data coming in from Elastic Defend.
26
27### Elastic Defend Integration Setup
28Elastic 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.
29
30#### Prerequisite Requirements:
31- Fleet is required for Elastic Defend.
32- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
33
34#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
35- Go to the Kibana home page and click "Add integrations".
36- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
37- Click "Add Elastic Defend".
38- Configure the integration name and optionally add a description.
39- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
40- 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).
41- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
42- 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.
43For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
44- Click "Save and Continue".
45- 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.
46For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
47"""
48severity = "high"
49tags = [
50    "Domain: Endpoint",
51    "OS: Linux",
52    "Use Case: Threat Detection",
53    "Tactic: Privilege Escalation",
54    "Use Case: Vulnerability",
55    "Data Source: Elastic Defend",
56]
57type = "eql"
58
59query = '''
60sequence by host.id, process.parent.entity_id with maxspan=5s
61  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
62    process.name == "enlightenment_sys" and process.args in ("/bin/mount/", "-o","noexec","nosuid","nodev","uid=*") ]
63  [process where host.os.type == "linux" and event.action == "uid_change" and event.type == "change" and user.id == "0"]
64'''
65
66
67[[rule.threat]]
68framework = "MITRE ATT&CK"
69[[rule.threat.technique]]
70id = "T1068"
71name = "Exploitation for Privilege Escalation"
72reference = "https://attack.mitre.org/techniques/T1068/"
73
74
75[rule.threat.tactic]
76id = "TA0004"
77name = "Privilege Escalation"
78reference = "https://attack.mitre.org/tactics/TA0004/"