Загрузка видео...

Не удалось загрузить видео

На главную

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

11,246 просмотров • 19 дней назад •via X (Twitter)

Комментарии: 12

Фото профиля Sarcastic Geek
Sarcastic Geek19 дней назад

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

Фото профиля Azino Oreva
Azino Oreva18 дней назад

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
Olu19 дней назад

Equivalent of CSRF on the client side

Фото профиля Limah Temitope
Limah Temitope19 дней назад

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

Фото профиля Duade Isaac
Duade Isaac18 дней назад

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

Фото профиля dTechGuy
dTechGuy17 дней назад

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
Denko19 дней назад

E b like you no wan respond to my dm 😢

Фото профиля Daniel Asaboro
Daniel Asaboro17 дней назад

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

Фото профиля The Tech Prophet (Amospikins)
The Tech Prophet (Amospikins)17 дней назад

Yes IEM

Фото профиля Azino Oreva
Azino Oreva18 дней назад

I think response models really prevents this a lot.

Фото профиля Lord Herrschaft👑⚔️
Lord Herrschaft👑⚔️19 дней назад

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

Фото профиля Jachi
Jachi17 дней назад

Just like social engineering your own application

Похожие видео