1. Srinivas Balivada USC CSCE548 07/22/2016

2.  Cookies are generally set server-side using the ‘Set-Cookie’ HTTP header and sent to the client  In PHP to set arguments for cookies : setcookie( name, value, expire, path, domain, secure, httponly);  SSL/TLS can be used to prevent this by encrypting the network packets,

3.  How to Predict session ID value ?

4.  A malicious user connects to the server and provides his valid credentials. He gets an identifier value, 7625, back from the server. This value might be in the form of a URL or a cookie. He then closes the browser and tries again with the same valid username and password. This time he gets the value 7627 back. It looks like this is an incrementing value, and someone else possibly logged on between the first user’s two logons.  CVE-2005-1784 is an practical example of sin

6.  Code Review ◦ Code Review is the best way to detect the attack. ◦ Tools such as TamperIE and Fiddler are used to detect the attack

7.  Use SSL, TLS, IPSec or any other encryption technology.  Hash the hashing of the concatenated string to mitigate this attack.

8.  Attacker Modifies Data: ◦ Message authentication code (MAC)

9.  Attacker predicts the data: ◦ The connection identifier using cryptographically random numbers can be used to solve this problem.

10.  Do test all web input, including forms and cookies with malicious input.  Do not embed confidential data in any HTTP or HTML construct.  Do not trust any data, confidential or not, in a web form, because malicious.

11. [1] M. Howard, D. LeBlanc, and J. Viega, 24 deadly sins of software security: programming flaws and how to fix them. New York: McGraw-Hill, 2010. [2] https://www.owasp.org/index.php/Session_Predictio n [3] https://en.wikipedia.org/wiki/Session_hijacking