OAuth 2.0 for Hackers (Part 2): How to Hack With Insecure OAuth 2 Endpoints

Поділитися
Вставка
  • Опубліковано 21 лис 2024

КОМЕНТАРІ • 15

  • @ethicalpap
    @ethicalpap  3 місяці тому +4

    Yall, I got a new camera and didn't realize it was zoomed into my face so much, until after the fact. Enjoy the close up.

    • @GreatAllen-p4m
      @GreatAllen-p4m 3 місяці тому

      no problem fam

    • @brandonkimm2227
      @brandonkimm2227 3 місяці тому

      as a fellow IT dude realizing how underesprented i am in the field, I came here for this

  • @kittoh_
    @kittoh_ 3 місяці тому

    Awesome stuff boss! Waiting for part III. 💯

  • @cheffloppa1
    @cheffloppa1 3 місяці тому

    🔥

  • @abduldione1524
    @abduldione1524 3 місяці тому +1

    great content

  • @systemsadministrator2419
    @systemsadministrator2419 3 місяці тому

    🎉

  • @uzumakiuchiha7678
    @uzumakiuchiha7678 3 місяці тому +1

    Provide link to part 1 in description please

  • @disrael2101
    @disrael2101 3 місяці тому +1

    sir are you offering any reverse eng bootcamp by any chance? i'm willing to enroll and pay for it!

  • @jpphoton
    @jpphoton 3 місяці тому +1

    client id is a weak point over http .. oauth perhaps could be further constrained by imposing a http header say like x-forwarded-for .. but that can be spoofed .. so it ends up being forever non-deterministic .. otherwise we'd have already locked it down .. but alas

    • @ethicalpap
      @ethicalpap  3 місяці тому

      Yep! Client-ID In cleartext is very bad and x-forwarded-for can also lead to SSRF. Love the input here!

  • @StynerDevHub
    @StynerDevHub 3 місяці тому

    🎉🎉🎉