Тёмный

OWASP API Top 10 - Broken Authentication 

Medusa
Подписаться 4,1 тыс.
Просмотров 956
50% 1

Опубликовано:

 

8 сен 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 15   
@bertrandfossung1216
@bertrandfossung1216 Месяц назад
Médusa you’re just the best. Your explanations of complex processes are second to none. Please keep up with this series. This is a real gem 💎
@Medusa0xf
@Medusa0xf Месяц назад
Means a lot 💚
@abdullahjaved2371
@abdullahjaved2371 Месяц назад
The time it'd have taken to edit this, goddamn. Keep up the content meds.
@Medusa0xf
@Medusa0xf Месяц назад
Thanks ❤
@amoh96
@amoh96 Месяц назад
i really like this type of video really cool keep it like this simple and give us examples thank u
@Medusa0xf
@Medusa0xf Месяц назад
glad!
@jxkz7
@jxkz7 Месяц назад
Great content ❤
@Medusa0xf
@Medusa0xf Месяц назад
thank you!
@crueljed1
@crueljed1 Месяц назад
Nice explanation ❤
@Medusa0xf
@Medusa0xf Месяц назад
Hope it helped!
@IBO.ATTACKS
@IBO.ATTACKS Месяц назад
شكرا؟ = thanks 🤩
@thechannelofmine
@thechannelofmine Месяц назад
The second report is closed as informative that means it's not a valid bug. for this to be impactful the attacker has to redirect the user to his malicious page than steal those tokens using the Referer header from the victim request.
@Medusa0xf
@Medusa0xf Месяц назад
that's another case in itself 😄
@thechannelofmine
@thechannelofmine Месяц назад
@@Medusa0xf If you take a look again at the report you will see that it's closed as informative that means it's not a vulnerability, as he didn't show a real exploit senario, and it's not vulnerable to man-in-the-middle attack because it's secured as https method. Btw are you active on hackerone?
@arjuna902-
@arjuna902- Месяц назад
i love your voice
Далее