Session Attacks

on


  1. Session ID : -
    1. Represents user - important as username password
    2. Session ID should be -
      1. Unique
      2. Random
      3. Unpredictable
      4. Long
      5. HTTPS transport
      6. Expiry date of session.
  2. Session Fixation: -
    1. Server provides an anonymous session ID for application before login and after login it should be changed always.
    2. Session fixation vulnerability occurs when anonymous session ID is upgraded to login session ID (for login, session ID does not change).
    3. Sometimes the server accepts arbitrary session IDs from users as well.
  3. Demo: -
    1. Session mgmt - session ID in url
    2. ID will be available in log files of the server if it is in url
    3. Need an application to do a demo, put in we: -
    4. https://github.com/appingmap/SessionFixation


Comments

Post a Comment