Dev.to Security 🔐 Cybersecurity 👁 0

IIS foothold to SYSTEM in 17 minutes: the integrity-level jump in logs

The scenario is fictional (RFC 5737 IPs). Windows events come from the book, not a live test. No exploit steps. On Windows, escalation shows up as: a low-privilege service spawned a System-integrity child. Wh

The scenario is fictional (RFC 5737 IPs). Windows events come from the book, not a live test. No exploit steps.

On Windows, escalation shows up as: a low-privilege service spawned a System-integrity child.

What you'll learn

  • Token, privileges, integrity levels (Low < Medium < High < System)
  • The jump in 4672 / 4688
  • Separating facts from hypotheses
  • What follows escalation

Timeline (win-web01, UTC)

Time Source Event
01:05:12 4624 web app pool logon from 203.0.113.77
01:14:20 4672 SeImpersonate / AssignPrimaryToken assigned to svc_web
01:14:21 4688 / Sysmon 1 w3wp.exe -> System-integrity ps.exe
01:16:40 7045 service WinTelemetrySvc from C:\Windows\Temp\wts.exe
01:17:11 4688 reg save HKLM\SAM

Normal: services.exe -> svchost.exe in a standard path. Attack: w3wp.exe (Medium) -> System child in a temp path.

Facts: the events above. Hypotheses: ps.exe is a token-impersonation tool (verify hash/signature); the SAM save aims at lateral movement.

Enable command-line logging for 4688 in advance; it is off by default.

Next: service hijacking and unquoted paths.

Adapted from chapter 25 of my Japanese book on server defense.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.