Tech moves fast! Stay ahead of the curve with Techopedia!
Join nearly 200,000 subscribers who receive actionable tech insights from Techopedia.
Web developers are especially wary of session hijacking because the HTTP cookies that are used to sustain a website session can be bootlegged by an attacker.
In the early days, HTTP protocol didn’t support cookies and therefore Web servers and browsers did not contain HTTP protocol. The evolution of session hijacking began in 2000 when HTTP 1.0 servers were implemented. HTTP 1.1 has been modified and modernized to support super cookies which have resulted in Web servers and Web browsers becoming more vulnerable to session hijacking.
Web developers can enlist certain techniques to help avoid session hijacking of their sites, including encryption methods and using long, random numbers for the session keys. Other solutions are to change cookie value requests and implement session regenerations after logins. Firesheep, a Firefox extension, has enabled public user session hijacking attacks by permitting access to personal cookies. Social network websites such as Twitter and Facebook are also vulnerable when users add them to their preferences.