1_3_5 Section 1 – Attacks, Threats, and Vulnerabilities - 1.3 – Application Attacks - Replay Attacks

What protocol should be used to prevent attackers from gathering session IDs off network flows?

How might an attacker gather session information directly from the network?

What action could an attacker with access to a vulnerable server take to obtain session IDs?

How can replay and session attacks be prevented?

What additional overhead does turning on encryption on a web server introduce?

What can users do if a service doesn't support HTTPS for communication?

What is a common piece of information that a crafty hacker might extract from network flows?

How might a hacker gather network information if they have physical access to the network?

What is a method a hacker might use if they lack physical access to the network?

What type of attack involves capturing and replaying information across the network as if it originated from the victim?

What can hackers do with gathered session IDs or credentials from network traffic?

Is physical access to the network always required for a replay attack to be successful?

What type of attack involves an attacker gaining access to the hash value associated with a password?

How can developers prevent a 'pass the hash' attack?

What technique involves adding a unique identifier to a hash to prevent a replay attack?

Why is it important for developers to ensure that cookies are secure?

How does an attacker gain access to a session ID in a session hijacking attack?

What makes SSL and TLS effective in preventing certain types of attacks?

Which of the following is NOT a reason why an attacker might target browser cookies?

What is the main risk of an attacker successfully performing a 'pass the hash' attack?

How can developers make session IDs more secure against hijacking?

'Pass the hash' attacks are mitigated by:

What does a crafty hacker aim to gather from network flows for an advantage during an attack?

How might an attacker gather network information if they lack physical access to the network?

What type of attack involves capturing information across the network and replaying it to seem as if it originated from the victim?

What method might an attacker use to redirect network information logically?

In a replay attack, what can be captured by the attacker and later used across the network?

What can an attacker do if they capture information that can be replayed across the network?

How can replay and session attacks be prevented?

What action could an attacker with access to a vulnerable server take to obtain session IDs?

What technique could prevent attackers from capturing session IDs from network flows?

Why is it important for websites to operate over HTTPS or TLS?

If a service does not support HTTPS, what alternative could be used to secure part of the communication flow?

What could an attacker do in real time to modify headers being sent to a server?

How can developers prevent a 'pass the hash' attack as described in the text?

What technique could developers use to make session IDs more secure against hijacking?

Why is salting the hash with a session ID helpful in preventing replay attacks?

What is a key benefit of using SSL or TLS for communication between client and server?

How does an attacker potentially gain access to a user's account on a server in a 'pass the hash' attack?

What makes cookies stored in web browsers vulnerable to replay attacks as mentioned in the text?

Why are session IDs important in communication between a client and a service as outlined in the text?

'Pass the hash' attacks involve replaying what type of information back to the server?

What role do cookies play in facilitating session hijacking attacks as discussed in the text?

How does salting the hash with a session ID protect against replay attacks, according to the information provided?