Skip to content

CornCon_11 FRI-T2-9:00 David Garlak & Jon Schnell Chasing SSRF in Downstream Asynchronous Workflows

Analysts investigate attack surfaces and defenses concerning CornCon_11 FRI-T2-9:00 David Garlak & Jon Schnell Chasing SSRF in Downstream Asynchronous Workflows.

Summary

SSRF Basics

David Garlak and Jon Schnell of Rapid7 define server-side request forgery as an injection point where the server fetches attacker-chosen URLs—acting as a proxy to internal or external resources. Variants include open redirects, file/SMB schemes, weak credentials, and cloud metadata misconfigurations.

Transparency Levels

They categorize transparent SSRF (attacker sees full response), semi-blind (DNS or partial hits only), and blind SSRF (no outbound visibility, requiring side channels). These labels frame later discussion of asynchronous workflows.

Defense Layers

Mitigations start with strict URL allowlisting—not denylisting—and careful URI parsing quirks. Response validation matters: teams often validate inbound input but trust fetched content. Network isolation and tight egress filtering reduce semi-blind callbacks.

Async Workflow Angle

The core topic is SSRF in downstream asynchronous jobs—webhooks, profile image fetchers, and background tasks where the request and response are decoupled. Attackers abuse delayed or blind fetches where traditional synchronous SSRF testing fails, demanding correlation across job queues and egress logs.

Related talks