Search

How Application Are Vulnerable For Improper Session Management | Securium Solutions

Greeting Everyone ! Hope Everything Is Going Well Today In This Blog We Will Explore Common Security Issue Which related To Weak Session Implementation  Comes Under  Session management Which Contain Different Attack Scenario Such As Session Related issue , Improper Validation Of Session Time Out , Session Not Implement Properly etc. Which Carries Critical Impact For Web Application .

What Are Common Vulnerability Comes Under Session Management :
Improper Session Management Includes Issue As Above List .

Testing for Session Management Schema:

Every Web Application Maintain Session Management Mechanism Which Improve User Experience With Application . In Session Management Mechanism . In Every Website For Better User Interaction It Use Cookie Or Unique Token Which Validate user Route Which Basically Call As Session Mechanism Schema against our target Website .

Sometime Web Application Fail to Protect Against Secure Session Schema Which An attacker Can Misuse This issue

Cookies are used to implement session. when a user accesses an application which needs to keep track of the user actions and verify  that user across multiple requests, a cookie (or cookies) is generated by the server and sent to the client.

Test Against Session Management Schema ?
  • Set-Cookie directives tagged as Secure
  • Is any Cookie operations take place over unencrypted transport.
  • Can the Cookie be forced over unencrypted transport
  • Expires= times are used on persistent cookies Which Contain Session Expire
  • Check Is Cookie Is Set As User Name or Which exposed User PII .
Testing for Session Fixation:

Session Fixation which Lead huge Impact For An Application If it Not Implemented Properly  Session fixation is enabled by the insecure practice of preserving the same value of the session cookies before and after authentication that mean cookie is valid after user logout  And Which possible to re use . That allows one person to fixate another person’s session identifier.
This Vulnerability  an attacker can obtain a set of session cookies from the target website without first authenticating. The attacker can then force these cookies into the victim’s browser using different techniques. If the victim later authenticates at the target website and the cookies are not refreshed upon login, the victim will be identified by the session cookies chosen by the attacker. The attacker is then able to impersonate the victim with these known cookies.

This Is How Session Fixation Work .

Testing for Logout Functionality

Session Logout Functionality Which Directly refer to User Signout Schema Which Mean That User End His session . In Some Web application Unbale To Protect against Logout Mechanism Which an attacker can exploit through weak session implementation schema .

session tokens decreases the likelihood of a successful session hijacking attack. This can be seen as a control against preventing other attacks like Cross Site Scripting and Cross Site Request Forgery. Such attacks have been known to rely on a user having an authenticated session present which user end By Own and it should re generate New Session .

This Refer An attacker can Re use same session token Or Cookie Value Which Victim Used Before While Victim logout from application .

Testing Session Timeout

Session Time out  mechanism which carries Huge Impact For Application If Web Application Fail to Protect against   Implementation Of Proper Time Set expiration  which may Lead To compromise User Account .

This An Attacker Can Perform Attack Such As MITM , Session Spoofing , XSS, CSRF And Able To manipulate User Session Which May Re useable And There Is No Proper Time Set Configured which May Be Client site or Server site .

Testing for Session Puzzling

Session Puzzling Attack is an application level vulnerability which can enable an attacker to perform a variety of malicious actions, including but not limited to:

  • Bypass efficient authentication enforcement mechanisms, and impersonate legitimate users.
  • Elevate the privileges of a malicious user account, in an environment that would otherwise be considered foolproof.
  • Skip over qualifying phases in multi-phase processes, even if the process includes all the commonly recommended code level restrictions.
  • Manipulate server-side values in indirect methods that cannot be predicted or detected.
  • Execute traditional attacks in locations that were previously unreachable, or even considered secure.

This Happens  when an application uses the same session for more than one purpose. An attacker can potentially access pages in an order unanticipated by the developers so that the session variable is set in one context and then used in another.

As Above We discuss Common Security Issue That Found Based On Session Management Schema Which Cause Damage Your Application And it will Lost Confidentiality, Integrity and Availability.

Conclusion : Today We Discussed About different Attack Phase Which Is Come Under Improper Session Management Schema We discussed Session time out , Improper Session handling On logout  And How Testing for Session Fixation attack .

Reference : OWASP

Table of Contents

Social Media
Facebook
Twitter
WhatsApp
LinkedIn