![]() SSL hijacking – the attacker generates a fake SSL certificate for the web application, and the victim then connects to a cloned or proxy application controlled by the attacker without any certificate warnings.SSL stripping – the attacker tricks the web application into dropping an HTTPS connection and using the insecure HTTP protocol instead, which makes packet sniffing possible.If a website or web application uses exclusively encrypted connections, simple cookie sniffing won’t work, but there are other tricks that may be attempted. ![]() This is especially common for public Wi-Fi networks. In the simplest case, when traffic is not encrypted, you only need a simple sniffer working in the same local network as the client to monitor network traffic for user connections and perform packet sniffing. Eavesdropping on communications – man-in-the-middle attacksĬookie hijacking techniques often rely on man-in-the-middle (MITM) attacks. ![]() There are four main approaches to cookie hijacking: eavesdropping on user communication, gaining access to the user’s computer, gaining access to the user’s browser data, or gaining access to the web server memory used to store cookies. While the hijacking techniques for such cookies will be the same as for web session cookies, the attacker may have a very different goal. For these apps, session hijacking attacks would use other techniques than cookie hijacking.Ĭookies are also used for other types of functionality than just working with browser sessions, so they may contain sensitive information other than session IDs. However, some web applications may handle session tokens in a different way, for example, using custom HTTP headers. In these cases, session hijacking uses the same techniques as cookie hijacking. Users’ session IDs, which are a common authentication mechanism for web apps, are most often handled using cookies. The terms cookie hijacking and session hijacking are closely related but are not the same. Note that you may see some web resources incorrectly using the term cookie poisoning for all attacks even loosely related to cookies, including various types of session hijacking and even session fixation or brute-force session prediction. Before poisoning a cookie, the attacker might also gain unauthorized access to the cookie content, but for some attacks, poisoning is possible even without accessing the content.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |