Potential Linux Credential Dumping via Unshadow

Identifies the execution of the unshadow utility which is part of John the Ripper, a password-cracking tool on the host machine. Malicious actors can use the utility to retrieve the combined contents of the '/etc/shadow' and '/etc/password' files. Using the combined file generated from the utility, the malicious threat actors can use them as input for password-cracking utilities or prepare themselves for future operations by gathering credential information of the victim.

Elastic rule (View on GitHub)

 1[metadata]
 2creation_date = "2023/02/27"
 3integration = ["endpoint"]
 4maturity = "production"
 5updated_date = "2024/05/21"
 6
 7[rule]
 8author = ["Elastic"]
 9description = """
10Identifies the execution of the unshadow utility which is part of John the Ripper, a password-cracking tool on the host
11machine. Malicious actors can use the utility to retrieve the combined contents of the '/etc/shadow' and '/etc/password'
12files. Using the combined file generated from the utility, the malicious threat actors can use them as input for
13password-cracking utilities or prepare themselves for future operations by gathering credential information of the
14victim.
15"""
16from = "now-9m"
17index = ["logs-endpoint.events.*", "endgame-*"]
18language = "eql"
19license = "Elastic License v2"
20name = "Potential Linux Credential Dumping via Unshadow"
21references = ["https://www.cyberciti.biz/faq/unix-linux-password-cracking-john-the-ripper/"]
22risk_score = 47
23rule_id = "e7cb3cfd-aaa3-4d7b-af18-23b89955062c"
24setup = """## Setup
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"""
49severity = "medium"
50tags = [
51    "Domain: Endpoint",
52    "OS: Linux",
53    "Use Case: Threat Detection",
54    "Tactic: Credential Access",
55    "Data Source: Elastic Defend",
56    "Data Source: Elastic Endgame",
57]
58timestamp_override = "event.ingested"
59type = "eql"
60
61query = '''
62process where host.os.type == "linux" and event.type == "start" and event.action in ("exec", "exec_event") and
63process.name == "unshadow" and process.args_count >= 3
64'''
65
66
67[[rule.threat]]
68framework = "MITRE ATT&CK"
69[[rule.threat.technique]]
70id = "T1003"
71name = "OS Credential Dumping"
72reference = "https://attack.mitre.org/techniques/T1003/"
73[[rule.threat.technique.subtechnique]]
74id = "T1003.008"
75name = "/etc/passwd and /etc/shadow"
76reference = "https://attack.mitre.org/techniques/T1003/008/"
77
78
79
80[rule.threat.tactic]
81id = "TA0006"
82name = "Credential Access"
83reference = "https://attack.mitre.org/tactics/TA0006/"

References

Related rules

to-top