The UI Performs the Wrong Action in livehelperchat/livehelperchat


Reported on

Oct 5th 2021

Sensitive data on the application can be exposed after the user logout

Proof of Concept
1 Login to the application (

2 Go to page like My Account , or Any other page

3 Click logout

4 Click browser back button

When a user logs out without closing the browser someone can view the information inside by clicking the back button on the browser.

About the vulnerability:
The back, forward and refresh buttons of the browser can be used to steal the password of a previous user. In this article we examine the vulnerability and look at ways to solve them.A web browser has the functionality to store the recent pages browsed by the user in its history. The back and forward buttons on the browser make use of this history to display the pages that the user visited recently. The browser also keeps track of the variables that were sent as part of the request to the server for each page. The refresh feature of the browser automates posting of the variables to the server thereby greatly improving the user experience while browsing.These features enhance the user experience but at the same time they expose a high risk vulnerability. This happens due to the application being insecurely designed. Attackers exploit these functionalities of the browser to obtain access to user credentials. Let’s see how this works and the solutions to overcome this problem.

Solution :use an intermediate page between the login page and the first page displayed after authentication.This intermediate page should be used to redirect the user via an “HTTP Redirect command” to  after successful login. In such a scenario, the login request is redirected immediately by the intermediate page. 2, use a salted hash technique for authentication. In this method, the password is hashed before sending it to the server. This hash is made random using a salt (a random value) provided by the server. This salt is added to the hash generated from the password and then hashed again. This salted hash is sent to the server for authentication. This way, even if the attacker uses the refresh button to capture the request, only the salted hash value will be visible. It will not allow the attacker to login by refreshing as the salt would change at the next login.
We have contacted a member of the livehelperchat team and are waiting to hear back a year ago
Remigijus Kiminas validated this vulnerability a year ago
@0xAmal has been awarded the disclosure bounty
The fix bounty is now up for grabs
Remigijus Kiminas marked this as fixed with commit 954337 a year ago
The fix bounty has been dropped
This vulnerability will not receive a CVE
to join this conversation