Linux Syslog Buffer Overflow Exploit Attempt Keywords

Alerts on Linux syslog entries containing known buffer overflow/stack-smashing attempt keyword patterns.

FreeReviewedSigma · High · v3
Product
linux
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2017-03-01
Updated
2026-07-31

ATT&CK techniques

Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags Linux log entries that contain specific text patterns associated with buffer overflow or stack-based code execution attempts. Such strings can indicate exploitation attempts like stack smashing or known exploit artifacts, which may precede memory corruption leading to process compromise. It relies on keyword matches in Unix system log sources to surface these patterns.

Related detections9 linkedT1068 — drag to rearrange
Suspicious Modification of Privileged Authentication Binaries via Kernel LPE
Malicious EDR Evasion Driver Load from AnyDesk Directory via k.sys (via image_load)
Malicious Zemana Vulnerable Driver Load for EDR Termination (via image_load)
Suspicious EDRKillShifter Vulnerable Driver Load from User Temp Directory (via image_load)
Suspicious Process Explorer Kernel Driver Dropped as PED.sys via File Creation (via file_event)
Malicious Payload Download From copy.fail Exploit Host on Linux (via process_creation)
Suspicious su Execution From Uncommon Parent Process on Linux (via process_creation)
Possible noPac sAMAccountName Spoofing via Machine Account Rename
Possible macOS TCC Bypass via mdimport Loading Custom Spotlight Importer
Linux Syslog Buffer Overflow Exploit Attempt Keywords
Pivot detection · T1068 · 9 related

Changelog

v3
  1. v3
    Candidate ingested via manual entry.2026-07-31
  2. v2
    Candidate ingested via manual entry.2026-07-31
  3. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.