Tag Info

New answers tagged

1

While the exact answer will depend on the technology you're using to process the request, the odds are that you can't split the header because modern frameworks have protection against response splitting. To exploit you need to find or create a vulnerable server that somehow allows the user to inject a CRLF into a cookie. Frequently this would be done with ...


1

I think that an HMAC provides little added security if the session ID is something that is hard to guess. For example, a long secure PRNG. But if the session ID is simple to guess then there is the risk of session hijacking. As the expressjs framework allows you to provide a session ID creation function that returns IDs with unknown security properties, an ...


0

I agree with monkeymagic's answer and assertion that "it's all about the data" and would definitely implement a secret token as Eric G suggested. You mentioned in a comment that SSN information is entered at some point so one additional step you can implement is to obscure any particularly sensitive information previously entered when a user resumes their ...


3

Answer 1: if the server uses SSL/HTTPS(verified by third party-not self-signed certificate), cookies and session IDs travel as cipher-text over the network, and if an attacker (Man in the Middle) uses a packet sniffer, they can not obtain any information. They can not decrypt data because the connection between client and server is secured by a verified ...


14

The connection between the client and the server does not use public key encryption (that is only used for the initial key exchange). A different algorithm is used for encryption (usually a symmetric encryption), such as AES-256-CBC on a TLS 1.2 connection. So unless you intercepted it, no one but the intended browser and the original server can decrypt the ...



Top 50 recent answers are included