Skip navigation
My challenge is actually based on a bug I found in Apollo Server; in its default configuration, it…
0:00 / 0:36

My challenge is actually based on a bug I found in Apollo Server; in its default configuration, it…

AmirMohammad Safari

@AmirMSafari8.4K followers

Visit on X
203 likesDownloadOriginal post

29,295 views

My challenge is actually based on a bug I found in Apollo Server; in its default configuration, it uses the same blacklist-based approach to prevent CSRF. I was able to bypass it and use it as an XS-Leak in default configs. I’ll be writing a detailed write-up soon about it :)

7 Comments

Comments from the original post on X (Twitter)

  • Yasho's profile picture

    @YShahinzadeh

    @omidxrz 👌🏻👌🏻

    6 likes

  • 3NTIT_Y's profile picture

    @entit_yy

    And I will be there in my best attire to read it!

    1 like

  • GURUN's profile picture

    @yadav_gurun

    lol blacklist CSRF defenses are always a ticking time bomb… feels inevitable someone turns it into something like this. @hud_hq would prob make that XS-leak path super obvious in traces, those weird cross-origin side effects tend to pop out fast when you actually watch the runtime flow

  • Person's profile picture

    @user826924

    Interesting stuff you're working on!

  • itsmeashu's profile picture

    @6173687561646d6

    how you guys able to understand the code , am asking like from beganining can you do a blog on it ?

  • soloboy's profile picture

    @alial1shan

    🔥🔥

  • Evan Klein's profile picture

    @EvanKlein338226

    Blacklist bypasses are underrated. So many devs think "check content-type" = secure. Can't wait for the writeup - XS-Leaks in default configs are gold for bug bounties 🔥