In this tutorial we focus on session ID
analysis. If you are not familiar with session ID’s I’ll do a quick
explanation. HTTP is a stateless protocol, so it’s equivalent to walkie
talkies or CB radios. You’ll send a request and wait for a reply, you
don’t have a constantly open communication line as you would with a
phone. So in order to emulate this open communication the HTTP protocol
uses session ID’s, commonly known as cookies. These cookies are simply
agreements between you and the web application that you are who you
claim to be. Once you have exchanged your cookie with the website you
can then talk back and forth as long as the cookie is tied to your
communication. So there’s the quick and dirty intro to session ID’s. So
the next logical question is how does this session ID process work or
even better how should it work? Let’s use a web mail application as an
example:
- You login to your web mail account
- Your web mail provider sends you a “random” cookie that is tied to your login session
- Each time you click on a new message within your Inbox your cookie is sent along to validate who you claim to be, that way you’ll get your next message and not another person’s message.