-
Notifications
You must be signed in to change notification settings - Fork 359
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2964 from splunk/gitlab_release_v4.25.0
Gitlab release v4.25.0
- Loading branch information
Showing
49 changed files
with
1,719 additions
and
731 deletions.
There are no files selected for viewing
Submodule contentctl
updated
43 files
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
57 changes: 57 additions & 0 deletions
57
detections/endpoint/connectwise_screenconnect_path_traversal.yml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
name: ConnectWise ScreenConnect Path Traversal | ||
id: 56a3ac65-e747-41f7-b014-dff7423c1dda | ||
version: 1 | ||
date: '2024-02-21' | ||
author: Michael Haag, Splunk | ||
data_source: | ||
- Sysmon Event ID 11 | ||
type: TTP | ||
status: production | ||
description: This analytic detects attempts to exploit the ConnectWise ScreenConnect CVE-2024-1708 vulnerability, which allows an attacker to perform path traversal attacks by manipulating the file_path and file_name parameters in the URL. The vulnerability, identified as critical with a CVSS score of 9.8, enables unauthorized users to access sensitive files and directories on the host system, potentially leading to the exfiltration of sensitive data or the execution of arbitrary code. The search query provided looks for file system events that could indicate exploitation attempts. This detection is crucial for identifying and responding to active exploitation of this vulnerability in environments running affected versions of ScreenConnect (23.9.7 and prior). It is recommended to update to version 23.9.8 or above immediately to remediate the issue, as detailed in the ConnectWise security advisory and further analyzed by Huntress researchers. | ||
search: '| tstats `security_content_summariesonly` count min(_time) as firstTime max(_time) as lastTime from datamodel=Endpoint.Filesystem where Filesystem.file_path IN ("*\\ScreenConnect\\App_Extensions\\*") Filesystem.file_name IN ("*.aspx","*.ashx") by Filesystem.file_create_time Filesystem.process_id Filesystem.process_guid Filesystem.file_name Filesystem.file_path Filesystem.dest | ||
| `drop_dm_object_name(Filesystem)` | ||
| `security_content_ctime(firstTime)` | ||
| `security_content_ctime(lastTime)` | ||
| `connectwise_screenconnect_path_traversal_filter`' | ||
how_to_implement: This analytic utilizes the Endpoint datamodel Filesystem node to identify path traversal attempts against ScreenConnect. Note that using SACL auditing or other file system monitoring tools may also be used to detect path traversal attempts. Typically the data for this analytic will come from EDR or other properly CIM mapped data sources. | ||
known_false_positives: False positives are not expected, as the detection is based on the presence of file system events that indicate path traversal attempts. The analytic may be modified to look for any file writes to this path as it is not common for files to write here. | ||
references: | ||
- https://www.huntress.com/blog/a-catastrophe-for-control-understanding-the-screenconnect-authentication-bypass | ||
- https://www.huntress.com/blog/detection-guidance-for-connectwise-cwe-288-2 | ||
- https://www.connectwise.com/company/trust/security-bulletins/connectwise-screenconnect-23.9.8 | ||
tags: | ||
analytic_story: | ||
- ConnectWise ScreenConnect Vulnerabilities | ||
asset_type: Endpoint | ||
confidence: 100 | ||
impact: 100 | ||
message: A path traversal attack against ScreenConnect has been detected on $dest$. | ||
mitre_attack_id: | ||
- T1190 | ||
observable: | ||
- name: dest | ||
type: Hostname | ||
role: | ||
- Victim | ||
product: | ||
- Splunk Enterprise | ||
- Splunk Enterprise Security | ||
- Splunk Cloud | ||
required_fields: | ||
- Filesystem.file_create_time | ||
- Filesystem.process_id | ||
- Filesystem.process_guid | ||
- Filesystem.file_name | ||
- Filesystem.file_path | ||
- Filesystem.dest | ||
risk_score: 100 | ||
security_domain: endpoint | ||
cve: | ||
- CVE-2024-1708 | ||
- CVE-2024-1709 | ||
tests: | ||
- name: True Positive Test | ||
attack_data: | ||
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1190/screenconnect/sysmon_app_extensions.log | ||
source: XmlWinEventLog:Microsoft-Windows-Sysmon/Operational | ||
sourcetype: xmlwineventlog |
61 changes: 61 additions & 0 deletions
61
detections/endpoint/connectwise_screenconnect_path_traversal_windows_sacl.yml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
name: ConnectWise ScreenConnect Path Traversal Windows SACL | ||
id: 4e127857-1fc9-4c95-9d69-ba24c91d52d7 | ||
version: 1 | ||
date: '2024-02-21' | ||
author: Michael Haag, Splunk | ||
data_source: | ||
- Windows Security 4663 | ||
type: TTP | ||
status: production | ||
description: This analytic detects attempts to exploit the ConnectWise ScreenConnect CVE-2024-1708 vulnerability utilizing Windows SACL EventCode 4663, which allows an attacker to perform path traversal attacks by manipulating the file_path and file_name parameters in the URL. The vulnerability, identified as critical with a CVSS score of 9.8, enables unauthorized users to access sensitive files and directories on the host system, potentially leading to the exfiltration of sensitive data or the execution of arbitrary code. The search query provided looks for file system events that could indicate exploitation attempts. This detection is crucial for identifying and responding to active exploitation of this vulnerability in environments running affected versions of ScreenConnect (23.9.7 and prior). It is recommended to update to version 23.9.8 or above immediately to remediate the issue, as detailed in the ConnectWise security advisory and further analyzed by Huntress researchers. | ||
search: '`wineventlog_security` EventCode=4663 ProcessName=*\\ScreenConnect.Service.exe file_path IN ("*\\ScreenConnect\\App_Extensions\\*") file_name IN ("*.aspx","*.ashx") | ||
| stats count min(_time) as firstTime max(_time) as lastTime by ObjectName ObjectType ProcessName AccessMask process_id EventCode Computer Caller_User_Name | ||
| rename Computer as dest Caller_User_Name as user ProcessName as process_name | ||
| `security_content_ctime(firstTime)` | ||
| `security_content_ctime(lastTime)` | ||
| `connectwise_screenconnect_path_traversal_windows_sacl_filter`' | ||
how_to_implement: To implement the following query, enable SACL auditing for the ScreenConnect directory(ies). With this data, the following analytic will work correctly. A GIST is provided in the references to assist with enabling SACL Auditing. | ||
known_false_positives: False positives should be limited as the analytic is specific to ScreenConnect path traversal attempts. Tune as needed, or restrict to specific hosts if false positives are encountered. | ||
references: | ||
- https://learn.microsoft.com/en-us/windows/security/threat-protection/auditing/event-4663 | ||
- https://www.huntress.com/blog/a-catastrophe-for-control-understanding-the-screenconnect-authentication-bypass | ||
- https://www.huntress.com/blog/detection-guidance-for-connectwise-cwe-288-2 | ||
- https://www.connectwise.com/company/trust/security-bulletins/connectwise-screenconnect-23.9.8 | ||
tags: | ||
analytic_story: | ||
- ConnectWise ScreenConnect Vulnerabilities | ||
asset_type: Endpoint | ||
confidence: 100 | ||
impact: 100 | ||
message: A path traversal attack against ScreenConnect has been detected on $dest$. | ||
mitre_attack_id: | ||
- T1190 | ||
observable: | ||
- name: dest | ||
type: Hostname | ||
role: | ||
- Victim | ||
product: | ||
- Splunk Enterprise | ||
- Splunk Enterprise Security | ||
- Splunk Cloud | ||
required_fields: | ||
- ObjectName | ||
- ObjectType | ||
- ProcessName | ||
- AccessMask | ||
- process_id | ||
- EventCode | ||
- Computer | ||
- Caller_User_Name | ||
risk_score: 100 | ||
security_domain: endpoint | ||
cve: | ||
- CVE-2024-1708 | ||
- CVE-2024-1709 | ||
tests: | ||
- name: True Positive Test | ||
attack_data: | ||
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1190/screenconnect/4663_connectwise_aspx_app_extensions.log | ||
sourcetype: XmlWinEventLog | ||
source: XmlWinEventLog:Security |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
61 changes: 61 additions & 0 deletions
61
detections/endpoint/windows_non_discord_app_access_discord_leveldb.yml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
name: Windows Non Discord App Access Discord LevelDB | ||
id: 1166360c-d495-45ac-87a6-8948aac1fa07 | ||
version: 1 | ||
date: '2024-02-16' | ||
author: Teoderick Contreras, Splunk | ||
data_source: | ||
- Windows Security 4663 | ||
type: Anomaly | ||
status: production | ||
description: The following analytic detects suspicious file access within the Discord LevelDB database. | ||
This database contains critical data such as user profiles, messages, guilds, channels, settings, and cached information. | ||
Access to this data poses a risk of Discord credential theft or unauthorized access to sensitive information on the | ||
compromised system. Detecting such anomalies can serve as an effective pivot to identify non-Discord applications | ||
accessing this database, potentially indicating the presence of malware or trojan stealers aimed at data theft. | ||
search: '`wineventlog_security` EventCode=4663 object_file_path IN ("*\\discord\\Local Storage\\leveldb*") | ||
AND process_name != *\\discord.exe AND NOT (process_path IN ("*:\\Windows\\System32\\*", "*:\\Windows\\SysWow64\\*", "*:\\Program Files*", "*:\\Windows\\*")) | ||
| stats count min(_time) as firstTime max(_time) as lastTime by object_file_name object_file_path process_name process_path process_id EventCode dest | ||
| `security_content_ctime(firstTime)` | ||
| `security_content_ctime(lastTime)` | ||
| `windows_non_discord_app_access_discord_leveldb_filter`' | ||
how_to_implement: To successfully implement this search, you must ingest Windows Security | ||
Event logs and track event code 4663. For 4663, enable "Audit Object Access" in | ||
Group Policy. Then check the two boxes listed for both "Success" and "Failure." | ||
known_false_positives: unknown | ||
references: | ||
- https://malpedia.caad.fkie.fraunhofer.de/details/win.404keylogger | ||
tags: | ||
analytic_story: | ||
- Snake Keylogger | ||
asset_type: Endpoint | ||
confidence: 30 | ||
impact: 30 | ||
message: A non-discord process $process_name$ accessing discord "leveldb" file on $dest$ | ||
mitre_attack_id: | ||
- T1012 | ||
observable: | ||
- name: dest | ||
type: Endpoint | ||
role: | ||
- Victim | ||
product: | ||
- Splunk Enterprise | ||
- Splunk Enterprise Security | ||
- Splunk Cloud | ||
required_fields: | ||
- _time | ||
- object_file_name | ||
- object_file_path | ||
- process_name | ||
- process_path | ||
- process_id | ||
- EventCode | ||
- dest | ||
risk_score: 9 | ||
security_domain: endpoint | ||
tests: | ||
- name: True Positive Test | ||
attack_data: | ||
- data: https://media.githubusercontent.com/media/splunk/attack_data/master/datasets/attack_techniques/T1552/snakey_keylogger_outlook_reg_access/snakekeylogger_4663.log | ||
source: XmlWinEventLog:Security | ||
sourcetype: XmlWinEventLog |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.