Potential Cookies Theft via Browser Debugging

Identifies the execution of a Chromium based browser with the debugging process argument, which may indicate an attempt to steal authentication cookies. An adversary may steal web application or service session cookies and use them to gain access web applications or Internet services as an authenticated user without needing credentials.

Elastic rule (View on GitHub)

 1[metadata]
 2creation_date = "2020/12/21"
 3integration = ["endpoint", "windows"]
 4maturity = "production"
 5updated_date = "2024/05/21"
 6
 7[rule]
 8author = ["Elastic"]
 9description = """
10Identifies the execution of a Chromium based browser with the debugging process argument, which may indicate an attempt
11to steal authentication cookies. An adversary may steal web application or service session cookies and use them to gain
12access web applications or Internet services as an authenticated user without needing credentials.
13"""
14false_positives = ["Developers performing browsers plugin or extension debugging."]
15from = "now-9m"
16index = ["auditbeat-*", "winlogbeat-*", "logs-endpoint.events.*", "logs-windows.*"]
17language = "eql"
18license = "Elastic License v2"
19max_signals = 33
20name = "Potential Cookies Theft via Browser Debugging"
21references = [
22    "https://github.com/defaultnamehere/cookie_crimes",
23    "https://embracethered.com/blog/posts/2020/cookie-crimes-on-mirosoft-edge/",
24    "https://github.com/rapid7/metasploit-framework/blob/master/documentation/modules/post/multi/gather/chrome_cookies.md",
25    "https://posts.specterops.io/hands-in-the-cookie-jar-dumping-cookies-with-chromiums-remote-debugger-port-34c4f468844e",
26]
27risk_score = 47
28rule_id = "027ff9ea-85e7-42e3-99d2-bbb7069e02eb"
29setup = """## Setup
30
31If enabling an EQL rule on a non-elastic-agent index (such as beats) for versions <8.2,
32events will not define `event.ingested` and default fallback for EQL rules was not added until version 8.2.
33Hence for this rule to work effectively, users will need to add a custom ingest pipeline to populate
34`event.ingested` to @timestamp.
35For more details on adding a custom ingest pipeline refer - https://www.elastic.co/guide/en/fleet/current/data-streams-pipeline-tutorial.html
36"""
37severity = "medium"
38tags = [
39    "Domain: Endpoint",
40    "OS: Linux",
41    "OS: Windows",
42    "OS: macOS",
43    "Use Case: Threat Detection",
44    "Tactic: Credential Access",
45    "Data Source: Elastic Defend",
46]
47timestamp_override = "event.ingested"
48type = "eql"
49
50query = '''
51process where event.type in ("start", "process_started", "info") and
52  process.name in (
53             "Microsoft Edge",
54             "chrome.exe",
55             "Google Chrome",
56             "google-chrome-stable",
57             "google-chrome-beta",
58             "google-chrome",
59             "msedge.exe") and
60   process.args : ("--remote-debugging-port=*",
61                   "--remote-debugging-targets=*",
62                   "--remote-debugging-pipe=*") and
63   process.args : "--user-data-dir=*" and not process.args:"--remote-debugging-port=0"
64'''
65
66
67[[rule.threat]]
68framework = "MITRE ATT&CK"
69[[rule.threat.technique]]
70id = "T1539"
71name = "Steal Web Session Cookie"
72reference = "https://attack.mitre.org/techniques/T1539/"
73
74
75[rule.threat.tactic]
76id = "TA0006"
77name = "Credential Access"
78reference = "https://attack.mitre.org/tactics/TA0006/"

References

Related rules

to-top