Use when test for Server-Side Request Forgery vulnerabilities by probing
Scanned 9/8/2026
Install to Claude Code
npx -y skills add oyi77/1ai-skills --skill performing-ssrf-vulnerability-exploitation --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Performing Ssrf Vulnerability Exploitation?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/oyi77-performing-ssrf-vulnerability-exploitation)More formats (shields.io, HTML) on the badges page.
---
name: performing-ssrf-vulnerability-exploitation
description: Use when test for Server-Side Request Forgery vulnerabilities by probing
cloud metadata endpoints, internal network services, and protocol handlers through
user-controllable URL parameters. Tests AWS/GCP/Azure metadata APIs (169.254.169.254),
internal port scanning via HTTP, URL scheme bypass techniques, and DNS rebinding
detection. Use when testing for server-side request forgery vulnerabilities by probing
cloud metadata.
domain: cybersecurity
tags:
- performing
- ssrf
- vulnerability
- exploitation
subdomain: security-operations
version: '1.0'
author: oyi77
license: Apache-2.0
nist_csf:
- DE.CM-01
- RS.MA-01
- GV.OV-01
- DE.AE-02
category: cybersecurity
---
# Performing Ssrf Vulnerability Exploitation
## Overview
Cybersecurity skill for performing ssrf vulnerability exploitation. Follows industry best practices and security standards.
## When to Use
**Trigger phrases:**
- "performing ssrf vulnerability exploitation"
- "Test for Server-Side Request Forgery vulnerabilities by probing cloud metadata e"
- When conducting security assessments that involve performing ssrf vulnerability exploitation
- When following incident response procedures for related security events
- When performing scheduled security testing or auditing activities
- When validating security controls through hands-on testing
## When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
## Prerequisites
- Familiarity with security operations 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
## 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. **Plan Operations** — Define objectives, scope, and success criteria for ssrf vulnerability exploitation operations.
2. **Prepare Environment** — Set up tools, access, and data sources required for ssrf vulnerability exploitation.
3. **Execute Core Workflow** — Perform the ssrf vulnerability exploitation operations following established procedures.
4. **Validate Results** — Verify that results meet quality standards and objectives.
5. **Report Findings** — Document results, observations, and recommendations.
6. **Follow Up** — Track remediation actions and verify fixes where applicable.
## Tools
- **Analysis Platform** — Data processing and visualization
- **Collaboration Tools** — Team coordination and knowledge sharing
## Process
1. **Reconnaissance** — Gather target information, identify attack surface, enumerate services
1. **Analysis/Exploitation** — Execute the technique, analyze results, document findings
1. **Reporting** — Document IOCs, write findings, provide remediation recommendations
## Verification
- [ ] All ssrf vulnerability exploitation procedures executed completely and documented
- [ ] Findings validated against multiple data sources
- [ ] False positives identified and filtered
- [ ] Results documented with evidence and timestamps
- [ ] Recommendations provided with risk-based prioritization
## 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. |Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!