Back to overview

Session management q

Every part of the application and type of request should verify that the user has a valid current session (if required) and thus their privileges, before undertaking any other data validation and processing.

NB: This relates to application-wide session management control. See SM K for what session management routines to use.

How to play?

Salim can bypass session management because it is not applied comprehensively and consistently across the application


Owasp ASVS (4.0): 1.1.6 ,3.7.1

Capec: 21

Owasp SCP: 58

Owasp Appsensor:

Safecode: 14,28

ASVS (4.0) Cheatsheetseries Index

ASVS V1.1 - Secure Software Development Lifecycle Requirements

ASVS V3.7 - Defenses Against Session Management Exploits


Cross-Site Scripting (XSS)

Password Guessing/Brute Force Attacks

Session Fixation

Session Hijacking (Man-in-the-Middle)

Error message exploitation

Loading comments 0%

Github logo View source on GitHub

Provided by dotNET lab

This website is created, hosted and provided by dotNET lab. dotNET lab provides training and guidance on secure software development. Contact us to get in touch!

OWASP Cornucopia

OWASP Cornucopia is originally created by Colin Watson. It is open source and can be downloaded free of charge from the OWASP website. It is is free to use. It is licensed under the Creative Commons Attribution-ShareAlike 3.0 license, so you can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one. OWASP does not endorse or recommend commercial products or services. OWASP Cornucopia is licensed under the Creative Commons Attribution-ShareAlike 3.0 license and is © 2012-2016 OWASP Foundation.