Course contentsShow
← Security
Lesson 886 of 3,05218. Web Security - CSRF and Request ForgeryFree lesson

Internal Network Enumeration via SSRF

Using SSRF to scan internal networks, identify services, and access resources behind firewalls.

Internal Network Enumeration via SSRF

You'll learn how attackers use SSRF to map out and probe internal networks that are normally hidden from the outside world.

When an attacker successfully exploits an SSRF vulnerability, they gain the server's ability to make requests—turning it into a "proxy" inside your network perimeter. This lets them explore and enumerate internal resources that external attackers should never reach.

How Internal Enumeration Works

Think of SSRF like giving someone your house keys: they can now open doors you normally keep locked. The vulnerable server sits inside your network, trusted by other internal systems, so it can reach:

  • Internal IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16)
  • Internal hostnames (database.internal, admin.local)
  • Services behind firewalls (databases, admin panels, internal APIs)

Common Enumeration Techniques

Attackers typically:

  1. Scan IP ranges: Probe 192.168.1.1 through 192.168.1.254 to identify live hosts
  2. Port scan discovered hosts: Check common ports (22, 80, 443, 3306, 5432, 8080)
  3. Service fingerprinting: Send requests to identify what services are running (Redis on 6379, MySQL on 3306)
  4. Access internal resources: Request internal documentation, APIs, or admin interfaces

For example, requesting http://192.168.1.15:8080/admin might reveal an unauthenticated internal admin panel, while http://192.168.1.20:3306 could expose a MySQL database accepting connections without proper authentication.

Why This Matters

Internal networks often have weaker security than internet-facing systems because they rely on network isolation for protection. SSRF breaks that assumption, bypassing firewalls entirely.

Key Takeaway: SSRF transforms an external attacker into an insider, enabling reconnaissance and access to internal services that should be isolated from the internet—making it critical to validate and restrict all server-side requests.