IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Setgid Bit Set via chmod Shell Execution via Apple Scripting »
Elastic Docs ›Elastic Security Solution [7.11] ›Detections and Alerts ›Prebuilt rule reference

Setuid Bit Set via chmod

edit

Setuid Bit Set via chmod

edit

An adversary may add the setuid bit to a file or directory in order to run a file with the privileges of the owning user. An adversary can take advantage of this to either do a shell escape or exploit a vulnerability in an application with the setuid bit to get code running in a different user’s context. Additionally, adversaries can use this mechanism on their own malware to make sure they’re able to execute in elevated contexts in the future.

Rule type: query

Rule indices:

  • auditbeat-*
  • logs-endpoint.events.*

Severity: low

Risk score: 21

Runs every: 5 minutes

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

Maximum alerts per execution: 33

Tags:

  • Elastic
  • Host
  • Linux
  • Threat Detection
  • Privilege Escalation

Version: 6 (version history)

Added (Elastic Stack release): 7.8.0

Last modified (Elastic Stack release): 7.11.2

Rule authors: Elastic

Rule license: Elastic License

Rule query

edit
event.category:process AND event.type:(start or process_started) AND
process.name:chmod AND process.args:(u+s OR /4[0-9]{3}/) AND NOT
user.name:root

Threat mapping

edit

Framework: MITRE ATT&CKTM

Rule version history

edit
Version 6 (7.11.2 release)
  • Formatting only
Version 5 (7.11.0 release)
  • Formatting only
Version 4 (7.10.0 release)
  • Formatting only
Version 3 (7.9.1 release)
  • Formatting only
Version 2 (7.9.0 release)

  • Updated query, changed from:

    event.action:(executed OR process_started) AND process.name:chmod AND
process.args:(u+s OR /4[0-9]{3}/) AND NOT user.name:root
« Setgid Bit Set via chmod Shell Execution via Apple Scripting »