Privilege Escalation via Named Pipe Impersonation

edit

Privilege Escalation via Named Pipe Impersonationedit

Identifies a privilege escalation attempt via named pipe impersonation. An adversary may abuse this technique by utilizing a framework such Metasploit’s meterpreter getsystem command.

Rule type: eql

Rule indices:

  • winlogbeat-*
  • logs-endpoint.events.*
  • logs-windows.*

Severity: high

Risk score: 73

Runs every: 5 minutes

Searches indices from: now-9m (Date Math format, see also Additional look-back time)

Maximum alerts per execution: 100

References:

Tags:

  • Elastic
  • Host
  • Windows
  • Threat Detection
  • Privilege Escalation

Version: 101 (version history)

Added (Elastic Stack release): 7.11.0

Last modified (Elastic Stack release): 8.5.0

Rule authors: Elastic

Rule license: Elastic License v2

Investigation guideedit


Rule queryedit

process where event.type == "start" and process.pe.original_file_name
in ("Cmd.Exe", "PowerShell.EXE") and process.args : "echo" and
process.args : ">" and process.args : "\\\\.\\pipe\\*"

Threat mappingedit

Framework: MITRE ATT&CKTM

Rule version historyedit

Version 101 (8.5.0 release)
  • Updated query, changed from:

    process where event.type in ("start", "process_started") and
    process.pe.original_file_name in ("Cmd.Exe", "PowerShell.EXE") and
    process.args : "echo" and process.args : ">" and process.args :
    "\\\\.\\pipe\\*"
Version 6 (8.4.0 release)
  • Updated query, changed from:

    process where event.type in ("start", "process_started") and
    process.pe.original_file_name in ("Cmd.Exe", "PowerShell.EXE") and
    process.args : "echo" and process.args : ">" and process.args :
    "\\\\.\\pipe\\*"
Version 4 (8.2.0 release)
  • Formatting only
Version 3 (7.12.0 release)
  • Formatting only
Version 2 (7.11.2 release)
  • Formatting only