Potential Code Execution via Postgresql

  1[metadata]
  2creation_date = "2022/06/20"
  3integration = ["endpoint"]
  4maturity = "production"
  5updated_date = "2025/02/04"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10This rule monitors for suspicious activities that may indicate an attacker attempting to execute arbitrary code within a
 11PostgreSQL environment. Attackers can execute code via PostgreSQL as a result of gaining unauthorized access to a public
 12facing PostgreSQL database or exploiting vulnerabilities, such as remote command execution and SQL injection attacks,
 13which can result in unauthorized access and malicious actions, and facilitate post-exploitation activities for
 14unauthorized access and malicious actions.
 15"""
 16from = "now-9m"
 17index = ["endgame-*", "logs-endpoint.events.process*"]
 18language = "eql"
 19license = "Elastic License v2"
 20name = "Potential Code Execution via Postgresql"
 21risk_score = 47
 22rule_id = "2a692072-d78d-42f3-a48a-775677d79c4e"
 23setup = """## Setup
 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 = "medium"
 49tags = [
 50    "Domain: Endpoint",
 51    "OS: Linux",
 52    "Use Case: Threat Detection",
 53    "Tactic: Execution",
 54    "Data Source: Elastic Endgame",
 55    "Data Source: Elastic Defend",
 56    "Resources: Investigation Guide",
 57]
 58timestamp_override = "event.ingested"
 59type = "eql"
 60
 61query = '''
 62process where host.os.type == "linux" and event.type == "start" and
 63event.action in ("exec", "exec_event", "fork", "fork_event") and user.name == "postgres" and (
 64  (process.parent.args : "*sh" and process.parent.args : "echo*") or
 65  (process.args : "*sh" and process.args : "echo*")
 66) and not (
 67  process.parent.name == "puppet" or
 68  process.command_line like (
 69    "*BECOME-SUCCESS-*", "bash -c while true; do sleep 1;*", "df -l", "sleep 1", "who", "head -v -n *", "tail -v -n *",
 70    "/bin/sh -c echo BECOME-SUCCESS*", "/usr/bin/python3 /var/tmp/ansible-tmp*"
 71  ) or
 72  process.parent.command_line like "*BECOME-SUCCESS-*"
 73)
 74'''
 75note = """## Triage and analysis
 76
 77> **Disclaimer**:
 78> This investigation guide was created using generative AI technology and has been reviewed to improve its accuracy and relevance. While every effort has been made to ensure its quality, we recommend validating the content and adapting it to suit your specific environment and operational needs.
 79
 80### Investigating Potential Code Execution via Postgresql
 81
 82PostgreSQL, a robust open-source database system, can be exploited by attackers to execute arbitrary code if they gain unauthorized access or exploit vulnerabilities like SQL injection. Adversaries may leverage command execution capabilities to perform malicious actions. The detection rule identifies suspicious processes initiated by the PostgreSQL user, focusing on shell executions that resemble command injection patterns, while excluding legitimate operations, to flag potential threats.
 83
 84### Possible investigation steps
 85
 86- Review the process details to confirm the presence of suspicious shell executions by the PostgreSQL user, focusing on processes with arguments containing "*sh" and "echo*".
 87- Check the parent process information to determine if the process was initiated by a known legitimate service, such as "puppet", or if it includes "BECOME-SUCCESS-" in the command line, which are excluded from the rule.
 88- Investigate the source of the PostgreSQL access to identify if it originated from an unauthorized or unusual IP address or user account.
 89- Analyze the timeline of events leading up to and following the alert to identify any patterns or additional suspicious activities that may indicate a broader attack.
 90- Correlate the alert with other security events or logs from the same host or network segment to assess if there are related indicators of compromise or ongoing threats.
 91
 92### False positive analysis
 93
 94- Puppet processes may trigger false positives due to their legitimate use of shell commands. To mitigate this, ensure that puppet-related processes are excluded by verifying that process.parent.name is set to "puppet".
 95- Automation tools that use shell scripts for configuration management might be flagged. Review and exclude these by checking for specific command patterns that are known to be safe, such as those containing "BECOME-SUCCESS".
 96- Scheduled maintenance scripts executed by the postgres user could be misidentified as threats. Identify these scripts and add them to an exclusion list based on their command line patterns.
 97- Regular database backup operations that involve shell commands might be mistakenly flagged. Document these operations and exclude them by matching their specific command line arguments.
 98- Custom monitoring scripts that execute shell commands under the postgres user should be reviewed and excluded if they are verified as non-malicious.
 99
100### Response and remediation
101
102- Immediately isolate the affected PostgreSQL server from the network to prevent further unauthorized access or malicious actions.
103- Terminate any suspicious processes identified by the detection rule to halt potential malicious activities.
104- Conduct a thorough review of the PostgreSQL server logs to identify any unauthorized access attempts or successful exploitations, focusing on the timeframes around the detected events.
105- Reset credentials for the PostgreSQL user and any other potentially compromised accounts to prevent further unauthorized access.
106- Apply the latest security patches and updates to the PostgreSQL server to mitigate known vulnerabilities that could be exploited.
107- Implement network segmentation to limit access to the PostgreSQL server, ensuring only authorized systems and users can connect.
108- Escalate the incident to the security operations team for further investigation and to assess the potential impact on other systems within the network."""
109
110[[rule.threat]]
111framework = "MITRE ATT&CK"
112
113[[rule.threat.technique]]
114id = "T1059"
115name = "Command and Scripting Interpreter"
116reference = "https://attack.mitre.org/techniques/T1059/"
117
118[[rule.threat.technique.subtechnique]]
119id = "T1059.004"
120name = "Unix Shell"
121reference = "https://attack.mitre.org/techniques/T1059/004/"
122
123[rule.threat.tactic]
124id = "TA0002"
125name = "Execution"
126reference = "https://attack.mitre.org/tactics/TA0002/"