Terminating User Sessions - Shezartech
post-template-default,single,single-post,postid-11426,single-format-standard,mkd-core-1.0.2,sparks child-child-ver-1.0.0,sparks-ver-1.5,mkd-smooth-scroll,mkd-smooth-page-transitions,mkd-ajax,mkd-grid-1300,mkd-blog-installed,mkd-header-standard,mkd-sticky-header-on-scroll-down-up,mkd-default-mobile-header,mkd-sticky-up-mobile-header,mkd-dropdown-default,mkd-header-style-on-scroll,mkd-full-width-wide-menu,mkd-header-standard-in-grid-shadow-disable,wpb-js-composer js-comp-ver-6.0.3,vc_responsive

Terminating User Sessions

Whenever a user logs into a web application, a session is created and maintained at the server-side. Sessions contain information about the user’s activities. As long as a session is alive, the user does not need to authenticate itself. Even when he/she had closed the webpage and is returning using the same device. That is possible when servers do not terminate the session, as the user moves from their portal or closes the browser. That is a vulnerability which a person with some technical expertise can exploit. An example illustrating the same is given below.

A user logs into a web application. A session is created upon successful authentication. That server does not terminate sessions when users leave the portal or close the browser/tab. An attacker wants to gain access to the user’s account. He infiltrates and observes the user’s communication with the web app. He obtains the URL of a payment transfer page along with other info needed to log in. The user closes the browser without logging out. The attacker then uses a software tool (like burp suite) to gain unauthorized access to the server using the URL. Then, he transfers money to another account.

The solution is to terminate user sessions as they move away from the portal or close the browser. Once a session ends, it is not possible to enter a URL and access the corresponding functionality. Authentication would be required.