File Creation by Cups or Foomatic-rip Child

  1[metadata]
  2creation_date = "2024/09/27"
  3integration = ["endpoint"]
  4maturity = "production"
  5updated_date = "2024/09/30"
  6
  7[rule]
  8author = ["Elastic"]
  9description = """
 10This detection rule addresses multiple vulnerabilities in the CUPS printing system, including CVE-2024-47176,
 11CVE-2024-47076, CVE-2024-47175, and CVE-2024-47177. Specifically, this rule detects suspicious file creation events
 12executed by child processes of foomatic-rip. These flaws impact components like cups-browsed, libcupsfilters, libppd,
 13and foomatic-rip, allowing remote unauthenticated attackers to manipulate IPP URLs or inject malicious data through
 14crafted UDP packets or network spoofing. This can result in arbitrary command execution when a print job is initiated.
 15"""
 16from = "now-9m"
 17index = ["logs-endpoint.events.*"]
 18language = "eql"
 19license = "Elastic License v2"
 20name = "File Creation by Cups or Foomatic-rip Child"
 21note = """## Triage and analysis
 22
 23### Investigating File Creation by Cups or Foomatic-rip Child
 24
 25This rule identifies potential exploitation attempts of several vulnerabilities in the CUPS printing system (CVE-2024-47176, CVE-2024-47076, CVE-2024-47175, CVE-2024-47177). These vulnerabilities allow attackers to send crafted IPP requests or manipulate UDP packets to execute arbitrary commands or modify printer configurations. Attackers can exploit these flaws to inject malicious data, leading to Remote Code Execution (RCE) on affected systems.
 26
 27#### Possible Investigation Steps
 28
 29- Investigate the incoming IPP requests or UDP packets targeting port 631.
 30- Examine the printer configurations on the system to determine if any unauthorized printers or URLs have been added.
 31- Investigate the process tree to check if any unexpected processes were triggered as a result of IPP activity. Review the executable files for legitimacy.
 32- Check for additional alerts related to the compromised system or user within the last 48 hours.
 33- Investigate network traffic logs for suspicious outbound connections to unrecognized domains or IP addresses.
 34- Check if any of the contacted domains or addresses are newly registered or have a suspicious reputation.
 35- Retrieve any scripts or executables dropped by the attack for further analysis in a private sandbox environment:
 36- Analyze potential malicious activity, including:
 37  - Attempts to communicate with external servers.
 38  - File access or creation of unauthorized executables.
 39  - Cron jobs, services, or other persistence mechanisms.
 40
 41### Related Rules
 42- Cupsd or Foomatic-rip Shell Execution - 476267ff-e44f-476e-99c1-04c78cb3769d
 43- Printer User (lp) Shell Execution - f86cd31c-5c7e-4481-99d7-6875a3e31309
 44- Network Connection by Cups or Foomatic-rip Child - e80ee207-9505-49ab-8ca8-bc57d80e2cab
 45- Suspicious Execution from Foomatic-rip or Cupsd Parent - 986361cd-3dac-47fe-afa1-5c5dd89f2fb4
 46
 47### False Positive Analysis
 48
 49- This activity is rarely legitimate. However, verify the context to rule out non-malicious printer configuration changes or legitimate IPP requests.
 50
 51### Response and Remediation
 52
 53- Initiate the incident response process based on the triage outcome.
 54- Isolate the compromised host to prevent further exploitation.
 55- If the investigation confirms malicious activity, search the environment for additional compromised hosts.
 56- Implement network segmentation or restrictions to contain the attack.
 57- Stop suspicious processes or services tied to CUPS exploitation.
 58- Block identified Indicators of Compromise (IoCs), including IP addresses, domains, or hashes of involved files.
 59- Review compromised systems for backdoors, such as reverse shells or persistence mechanisms like cron jobs.
 60- Investigate potential credential exposure on compromised systems and reset passwords for any affected accounts.
 61- Restore the original printer configurations or uninstall unauthorized printer entries.
 62- Perform a thorough antimalware scan to identify any lingering threats or artifacts from the attack.
 63- Investigate how the attacker gained initial access and address any weaknesses to prevent future exploitation.
 64- Use insights from the incident to improve detection and response times in future incidents (MTTD and MTTR).
 65"""
 66references = [
 67    "https://www.elastic.co/security-labs/cups-overflow",
 68    "https://www.evilsocket.net/2024/09/26/Attacking-UNIX-systems-via-CUPS-Part-I/",
 69    "https://gist.github.com/stong/c8847ef27910ae344a7b5408d9840ee1",
 70    "https://github.com/RickdeJager/cupshax/blob/main/cupshax.py",
 71]
 72risk_score = 73
 73rule_id = "b9b14be7-b7f4-4367-9934-81f07d2f63c4"
 74setup = """## Setup
 75
 76This rule requires data coming in from Elastic Defend.
 77
 78### Elastic Defend Integration Setup
 79Elastic 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.
 80
 81#### Prerequisite Requirements:
 82- Fleet is required for Elastic Defend.
 83- To configure Fleet Server refer to the [documentation](https://www.elastic.co/guide/en/fleet/current/fleet-server.html).
 84
 85#### The following steps should be executed in order to add the Elastic Defend integration on a Linux System:
 86- Go to the Kibana home page and click "Add integrations".
 87- In the query bar, search for "Elastic Defend" and select the integration to see more details about it.
 88- Click "Add Elastic Defend".
 89- Configure the integration name and optionally add a description.
 90- Select the type of environment you want to protect, either "Traditional Endpoints" or "Cloud Workloads".
 91- 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).
 92- We suggest selecting "Complete EDR (Endpoint Detection and Response)" as a configuration setting, that provides "All events; all preventions"
 93- 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.
 94For more details on Elastic Agent configuration settings, refer to the [helper guide](https://www.elastic.co/guide/en/fleet/8.10/agent-policy.html).
 95- Click "Save and Continue".
 96- 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.
 97For more details on Elastic Defend refer to the [helper guide](https://www.elastic.co/guide/en/security/current/install-endpoint.html).
 98"""
 99severity = "high"
100tags = [
101    "Domain: Endpoint",
102    "OS: Linux",
103    "Use Case: Threat Detection",
104    "Use Case: Vulnerability",
105    "Tactic: Execution",
106    "Data Source: Elastic Defend",
107]
108type = "eql"
109query = '''
110sequence by host.id with maxspan=10s
111  [process where host.os.type == "linux" and event.type == "start" and event.action == "exec" and
112   process.parent.name == "foomatic-rip" and
113   process.name in ("bash", "dash", "sh", "tcsh", "csh", "zsh", "ksh", "fish")] by process.entity_id
114  [file where host.os.type == "linux" and event.type != "deletion" and
115   not (process.name == "gs" and file.path like "/tmp/gs_*")] by process.parent.entity_id
116'''
117
118[[rule.threat]]
119framework = "MITRE ATT&CK"
120
121[[rule.threat.technique]]
122id = "T1203"
123name = "Exploitation for Client Execution"
124reference = "https://attack.mitre.org/techniques/T1203/"
125
126[rule.threat.tactic]
127id = "TA0002"
128name = "Execution"
129reference = "https://attack.mitre.org/tactics/TA0002/"