Exploiting Ms17 010 Eternalblue Vulnerability

---
name: exploiting-ms17-010-eternalblue-vulnerability
description: Use when mS17-010 (EternalBlue) is a critical vulnerability in Microsoft's
  SMBv1 implementation that allows remote code execution. Originally discovered by
  the NSA and leaked by the Shadow Brokers in 2017, it. Use when working with exploiting
  ms17 010 eternalblue vulnerability.
domain: cybersecurity
subdomain: red-teaming
tags:
- red-team
- adversary-simulation
- mitre-attack
- exploitation
- post-exploitation
- eternalblue
- smb
- remote-code-execution
version: '1.0'
author: oyi77
license: Apache-2.0
d3fend_techniques:
- Application Protocol Command Analysis
- Network Isolation
- Network Traffic Analysis
- Client-server Payload Profiling
- Platform Monitoring
nist_csf:
- ID.RA-01
- GV.OV-02
- DE.AE-07
category: cybersecurity
---

# Exploiting MS17-010 EternalBlue Vulnerability

## Overview

MS17-010 (EternalBlue) is a critical vulnerability in Microsoft's SMBv1 implementation that allows remote code execution. Originally discovered by the NSA and leaked by the Shadow Brokers in 2017, it was used in the WannaCry and NotPetya ransomware campaigns. Despite patches being available since March 2017, many organizations still have unpatched systems, making it a viable red team exploitation vector especially in legacy environments.


## When to Use
**Trigger phrases:**
- "exploiting ms17 010 eternalblue vulnerability"
- "MS17-010 (EternalBlue) is a critical vulnerability in Microsoft's SMBv1 implemen"


- When performing authorized security testing that involves exploiting ms17 010 eternalblue vulnerability
- When analyzing malware samples or attack artifacts in a controlled environment
- When conducting red team exercises or penetration testing engagements
- When building detection capabilities based on offensive technique understanding

## Prerequisites

- Familiarity with red teaming concepts and tools
- Access to a test or lab environment for safe execution
- Python 3.8+ with required dependencies installed
- Appropriate authorization for any testing activities

## MITRE ATT&CK Mapping

- **T1210** - Exploitation of Remote Services
- **T1190** - Exploit Public-Facing Application
- **T1569.002** - System Services: Service Execution

## Workflow

```python
# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
```

1. **Scope and authorize** — confirm written authorization and define target boundaries
2. **Reconnaissance** — enumerate targets, services, and potential attack surfaces
3. **Exploitation** — attempt exploitation of identified vulnerabilities within scope
4. **Post-exploitation** — document access level, lateral movement, and data exposure
5. **Report and remediate** — compile findings with reproduction steps and fix recommendations
### Phase 1: Vulnerability Scanning
1. Scan target networks for SMB port 445
2. Check for SMBv1 protocol support
3. Run MS17-010 vulnerability check (Nmap NSE script or Metasploit auxiliary)
4. Document vulnerable systems with OS version and patch level

### Phase 2: Exploitation
1. Select appropriate exploit variant based on target OS
2. Configure exploit payload (Meterpreter, Cobalt Strike beacon, custom shellcode)
3. Execute exploit against confirmed vulnerable target
4. Verify code execution and establish session

### Phase 3: Post-Exploitation
1. Establish persistence on compromised system
2. Dump credentials from memory
3. Use compromised host as pivot point
4. Document exploitation evidence

## When NOT to Use

- You don't have explicit authorization to exploit
- Task is about detecting exploits, not performing them (use detecting-* skills)
- You need to analyze exploit artifacts (use analyzing-* skills)
- Task is about building exploit tools (use building-* skills)
- Target is production without authorization
- Task requires responsible disclosure (follow disclosure process)


## Red Flags

- Performing actions without explicit written authorization from the asset owner
- Testing against production systems without a defined scope and rules of engagement
- Exceeding the authorized scope of the engagement
- Leaving persistent access mechanisms without explicit approval
- Causing denial-of-service on production systems during testing

## Verification

- All steps executed successfully against a test environment before production use
- Output documented with screenshots or logs demonstrating expected behavior
- All exploited vulnerabilities documented with reproduction steps
- Scope boundaries confirmed — only authorized targets were tested
- Remediation recommendations included for every finding

## Tools and Resources

| Tool | Purpose |
|------|---------|
| Nmap ms-17-010 NSE scripts | Vulnerability detection |
| Metasploit ms17_010_eternalblue | Exploitation module |
| Metasploit ms17_010_psexec | Alternative exploitation |
| AutoBlue-MS17-010 | Standalone Python exploit |
| CrackMapExec | Mass SMB vulnerability scanning |

## Detection Indicators

- IDS/IPS signatures for EternalBlue exploit traffic
- SMBv1 negotiation from unusual source hosts
- Event ID 7045: New service installation after exploitation
- Anomalous named pipe activity on SMB
- Large SMB write requests characteristic of buffer overflow

## Validation Criteria

- [ ] Vulnerable systems identified via scanning
- [ ] Exploitation achieved on authorized target
- [ ] Code execution confirmed with session established
- [ ] Post-exploitation activities documented
- [ ] Remediation recommendations provided

## Process

1. Analyze the task requirements
2. Apply domain expertise
3. Verify output quality

## Anti-Rationalization Table

| Rationalization | Reality |
|---|---|
| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |
| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |