Applied Cybernetics Group
T1185 Browser Session Hijacking
- Technique
T1185- Tactics
- Collection
- Research, 90 days
- 0
- KEV CVEs mapped
- 3
- SigmaHQ rules
- 2
- Elastic, Splunk
- 11
- thrunt rules
- 0
- Upstream
- https://attack.mitre.org/techniques/T1185
MITRE description
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.(Citation: Wikipedia Man in the Browser) A specific example is when an adversary injects software into a browser that allows them to inherit cookies, HTTP sessions, and SSL client certificates of a user then use the browser as a way to pivot into an authenticated intranet.(Citation: Cobalt Strike Browser Pivot)(Citation: ICEBRG Chrome Extensions) Executing browser-based behaviors such as pivoting may require specific process permissions, such as <code>SeDebugPrivilege</code> and/or high-integrity/administrator rights. Another example involves pivoting browser traffic from the adversary's browser through the user's browser by setting up a proxy which will redirect web traffic. This does not alter the user's traffic in any way, and the proxy connection can be severed as soon as the browser is closed. The adversary assumes the security context of whichever browser process the proxy is injected into. Browsers typically create a new process for each tab that is opened and permissions and certificates are separated accordingly. With these permissions, an adversary could potentially browse to any resource on an intranet, such as [Sharepoint](https://attack.mitre.org/techniques/T1213/002) or webmail, that is accessible through the browser and which the browser has sufficient permissions. Browser pivoting may also bypass security provided by 2-factor authentication.(Citation: cobaltstrike manual)
KEV CVEs mapped to this technique
MITRE CTID maps these KEV CVEs to this technique by hand. They are the actively exploited vulnerabilities behind this technique's KEV signal.
Detection coverage
SigmaHQ community rules
- Potential Data Stealing Via Chromium Headless Debugging (core)
- Browser Started with Remote Debugging (core)
Elastic and Splunk rules
- Manual Loading of a Suspicious Chromium Extension (elastic)
- Browser Process Spawned from an Unusual Parent (elastic)
- ASL AWS Concurrent Sessions From Different Ips (splunk)
- AWS Concurrent Sessions From Different Ips (splunk)
- Azure AD Concurrent Sessions From Different Ips (splunk)
- O365 Concurrent Sessions From Different Ips (splunk)
- Windows Browser Process Launched with Unusual Flags (splunk)
- Windows Chrome Auto-Update Disabled via Registry (splunk)
- Windows Chrome Enable Extension Loading via Command-Line (splunk)
- Windows Chrome Extension Allowed Registry Modification (splunk)
- Windows Chromium Process Loaded Extension via Command-Line (splunk)