Potential Privilege Escalation via Linux DAC permissions

Identifies potential privilege escalation exploitation of DAC (Discretionary access control) file permissions. The rule identifies exploitation of DAC checks on sensitive file paths via suspicious processes whose capabilities include CAP_DAC_OVERRIDE (where a process can bypass all read write and execution checks) or CAP_DAC_READ_SEARCH (where a process can read any file or perform any executable permission on the directories).

Elastic rule (View on GitHub)

 1[metadata]
 2creation_date = "2024/01/08"
 3integration = ["endpoint"]
 4maturity = "production"
 5min_stack_comments = "Linux effective and permitted process capability data sources were added in version 8.11.0"
 6min_stack_version = "8.11.0"
 7updated_date = "2024/01/08"
 8
 9[rule]
10author = ["Elastic"]
11description = """
12Identifies potential privilege escalation exploitation of DAC (Discretionary access control) file permissions. The rule
13identifies exploitation of DAC checks on sensitive file paths via suspicious processes whose capabilities
14include CAP_DAC_OVERRIDE (where a process can bypass all read write and execution checks) or
15CAP_DAC_READ_SEARCH (where a process can read any file or perform any executable permission on the directories).
16"""
17from = "now-9m"
18index = ["logs-endpoint.events.*"]
19language = "eql"
20license = "Elastic License v2"
21name = "Potential Privilege Escalation via Linux DAC permissions"
22risk_score = 47
23rule_id = "f7c70f2e-4616-439c-85ac-5b98415042fe"
24setup = """
25
26This rule requires data coming in from Elastic Defend.
27
28### Elastic Defend Integration Setup
29Elastic 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.
30
31#### Prerequisite Requirements:
32- Fleet is required for Elastic Defend.
33- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
34
35#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
36- Go to the Kibana home page and click "Add integrations".
37- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
38- Click "Add Elastic Defend".
39- Configure the integration name and optionally add a description.
40- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
41- 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).
42- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
43- 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.
44For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
45- Click "Save and Continue".
46- 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.
47For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
48
49"""
50severity = "medium"
51tags = ["Domain: Endpoint", "OS: Linux", "Use Case: Threat Detection", "Tactic: Privilege Escalation", "Data Source: Elastic Defend"]
52timestamp_override = "event.ingested"
53type = "eql"
54query = '''
55process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
56(process.thread.capabilities.permitted: "CAP_DAC_*" or process.thread.capabilities.effective: "CAP_DAC_*") and
57process.command_line : ("*sudoers*", "*passwd*", "*shadow*", "*/root/*") and user.id != "0"
58'''
59
60[[rule.threat]]
61framework = "MITRE ATT&CK"
62
63[[rule.threat.technique]]
64id = "T1068"
65name = "Exploitation for Privilege Escalation"
66reference = "https://attack.mitre.org/techniques/T1068/"
67
68[rule.threat.tactic]
69id = "TA0004"
70name = "Privilege Escalation"
71reference = "https://attack.mitre.org/tactics/TA0004/"

Related rules

to-top