Loading video...

Video Failed to Load

Go Home

The attacker cannot access your private network. Your backend can. That’s the SSRF problem

11,692 views • 1 month ago •via X (Twitter)

12 Comments

Sarcastic Geek's profile picture
Sarcastic Geek1 month ago

I said it in 2025 and they hosted a space for me, backend is more than just crud!

Azino Oreva's profile picture
Azino Oreva1 month ago

I sat down and try to reason why I would trust a user to input anything that I will run like a link or something. For files I simply return back the url let the user go get it himself. I think separating your server from media service is the smartest system makes it faster even.

Olu's profile picture
Olu1 month ago

Equivalent of CSRF on the client side

Limah Temitope's profile picture
Limah Temitope1 month ago

This is so good. Thanks for the information always boss.

Duade Isaac's profile picture
Duade Isaac1 month ago

lol, I was reading about SSRF this morning 😂 and this is what I see on my TL right after

dTechGuy's profile picture
dTechGuy1 month ago

XSRF CSRF SSRF All points to one thing "Never trust anything coming from the clients browser" However, your server shouldnt be handling static files though. Allow 3rd party apps handle them and you save the public URLs and ID. Save yourself all this stress.

Denko's profile picture
Denko1 month ago

E b like you no wan respond to my dm 😢

Daniel Asaboro's profile picture
Daniel Asaboro1 month ago

please what ear piece is that? is it for monitoring?

The Tech Prophet (Amospikins)'s profile picture
The Tech Prophet (Amospikins)1 month ago

Yes IEM

Azino Oreva's profile picture
Azino Oreva1 month ago

I think response models really prevents this a lot.

Lord Herrschaft👑⚔️'s profile picture
Lord Herrschaft👑⚔️1 month ago

It's crazy how your server can be used to attack your server

Jachi's profile picture
Jachi1 month ago

Just like social engineering your own application

Related Videos