Skip to content

Hacking HTTP Status Codes

schneier.com
8 pointstewks2 comments
On HN

Comments

Technical details here: https://grepular.com/Abusing_HTTP_Status_Codes_to_Expose_Pri...

The trick is to identify GET requests that will succeed only if the victim is logged into $SITE_OF_INTEREST, and bury them in an

   <img src="https://SITE_OF_INTEREST/more/stuff/here" 
        onload="is_logged_in()"
        onerror="not_logged_in()"
        ...>
If $SITE_OF_INTEREST doesn't have decent CSRF protection, this is an easy way for a rogue website to not only make a request, but observe the result.
AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.