I have built a WebApp on ASPNET Boilerplate fw and used protocol HTTPS. I used Burp Suite Community Edition to test and found a risk related to Replay Attack. The root cause is from Token based design, the token is not revoked after user logout. So is there any walkaround to overcome it?
Testing steps:
- Open Burp Suite
- Open browser, login into my WebApp
- Doing a task in the WebApp, ie Create new record
- Go to Burp, find HTTP request on my Create new record action in HTTP history, Send it to Repeater
- Logout, close browser
- Go to Burp/Repeater, re-send the HTTP request and receive HTTP/1.1 200 OK
- Checking database: The same record inserted
Could anyone give me some advices? Thanks