Detection: Linux Suspicious Redis Activity

Description

The following analytic detects Redis processes spawning a system shell command. This can indicate exploitation activity of a redis server to gain code execution.

Search

 1
 2| tstats `security_content_summariesonly`
 3  count min(_time) as firstTime
 4        max(_time) as lastTime
 5
 6FROM datamodel=Endpoint.Processes WHERE
 7
 8(
 9    Processes.parent_process_name IN (
10        "redis-sentinel",
11        "redis-server"
12    )
13    OR
14    Processes.parent_process_path = "*/bin/redis*"
15)
16
17Processes.process_name IN (
18    "awk", "bash", "curl", "dash", "gawk", "id", "ifconfig",
19    "lua", "nc", "ncat", "netcat", "openssl", "perl", "php",
20    "python", "python2", "python3", "ruby", "sh", "socat",
21    "wget", "whoami", "zsh"
22)
23
24BY Processes.action Processes.dest Processes.original_file_name
25   Processes.parent_process Processes.parent_process_exec Processes.parent_process_guid
26   Processes.parent_process_id Processes.parent_process_name Processes.parent_process_path
27   Processes.process Processes.process_current_directory Processes.process_exec
28   Processes.process_guid Processes.process_hash Processes.process_id
29   Processes.process_integrity_level Processes.process_name Processes.process_path
30   Processes.user Processes.user_id Processes.vendor_product
31
32
33| `drop_dm_object_name(Processes)`
34
35| `security_content_ctime(firstTime)`
36
37| `security_content_ctime(lastTime)`
38
39| `linux_suspicious_redis_activity_filter`

Data Source

Name	Platform	Sourcetype	Source
Sysmon for Linux EventID 1	Linux	'sysmon:linux'	'Syslog:Linux-Sysmon/Operational'

Macros Used

Annotations

CVE

• CVE-2022-0543

Default Configuration

This detection is configured by default in Splunk Enterprise Security to run with the following settings:

Implementation

The detection is based on data that originates from Endpoint Detection and Response (EDR) agents. These agents are designed to provide security-related telemetry from the endpoints where the agent is installed. To implement this search, you must ingest logs that contain the process GUID, process name, and parent process. Additionally, you must ingest complete command-line executions. These logs must be processed using the appropriate Splunk Technology Add-ons that are specific to the EDR product. The logs must also be mapped to the Processes node of the Endpoint data model. Use the Splunk Common Information Model (CIM) to normalize the field names and speed up the data modeling process.

Known False Positives

Legitimate administrative scripts or automated maintenance tasks may trigger this detection when managing Redis configurations or performing system operations. Filter based on known administrative activity and approved management tools.

Associated Analytic Story

• Command And Control

• Compromised Linux Host

• Linux Post-Exploitation

• Linux Living Off The Land

• Linux Privilege Escalation

• Linux Persistence Techniques

Finding

Threat Objects

References

• https://www.bleepingcomputer.com/news/security/new-p2pinfect-worm-malware-targets-linux-and-windows-redis-servers/

• https://thesecmaster.com/how-to-fix-cve-2022-0543-a-critical-lua-sandbox-escape-vulnerability-in-redis/

Detection Testing

Replay any dataset to Splunk Enterprise by using our replay.py tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

Source: GitHub |

Version: 1