🔒 Security & Privacy

Capital One's SSRF Nightmare: How One Bad URL Stole 100 Million Lives

Picture this: a hacker types a URL. Your server fetches it blindly. Boom—100 million credit apps, SSNs, gone. Capital One's SSRF screw-up wasn't rocket science; it was basic trust gone wrong.

Visual chain of Capital One SSRF attack from URL input to 100M records exfiltrated

⚡ Key Takeaways

  • SSRF via unvalidated URLs directly harvested AWS IAM creds from IMDSv1—no malware needed. 𝕏
  • IMDSv2 + URL allowlisting stops this cold; most breaches skip these basics. 𝕏
  • Cloud vendors profit from fixes—your breach is their business model. 𝕏
Written by

Priya Sundaram

Hardware and infrastructure reporter. Tracks GPU wars, chip design, and the compute economy.

Worth sharing?

Get the best Open Source stories of the week in your inbox — no noise, no spam.

Originally reported by Dev.to

Stay in the loop

The week's most important stories from Open Source Beat, delivered once a week.