Cyberstudy
PDF p.361 In progress

Replay Attacks

Open PDF at p.361 18 flashcards

Summary

PDF p.361

Replay attacks exploit cookie-based sessions in web applications by capturing or guessing session tokens and using them to reestablish sessions illegitimately. These attacks can be facilitated by on-path attacks, unsecured networks, malware, or cross-site scripting (XSS).

Detailed explanation

PDF p.361
  • HTTP and Cookies
    • Stateless Protocol: HTTP does not preserve client information.
    • Cookies: Used to maintain stateful data, created by the server and sent in HTTP response headers.
    • Types of Cookies
      • Nonpersistent: Stored in memory, deleted when the browser closes.
      • Persistent: Stored in the browser cache, deleted by the user or upon expiration.
  • Session Management
    • Session Tokens: Identify users and prove authentication across multiple actions and requests.
    • Replay Attack Mechanism: Capturing or guessing session tokens to reestablish sessions.
  • Methods of Capturing Cookies
    • On-Path Attacks: Sniffing network traffic.
    • Unsecured Networks: Public Wi-Fi hotspots.
    • Malware: Infecting the host to capture cookies.
    • Cross-Site Scripting (XSS): Running malicious code in a trusted site or application context.
  • Session Prediction Attacks
    • Focus: Identifying weaknesses in token generation algorithms.
    • Requirements: Non-predictable algorithms, no revealing information about the session client.
    • Session Management: Limit session lifespan, require reauthentication periodically.

Important terms

taken from the text above
Stateless Protocol
HTTP does not preserve client information.
Cookies
Used to maintain stateful data, created by the server and sent in HTTP response headers.
Nonpersistent
Stored in memory, deleted when the browser closes.
Persistent
Stored in the browser cache, deleted by the user or upon expiration.
Session Tokens
Identify users and prove authentication across multiple actions and requests.
Replay Attack Mechanism
Capturing or guessing session tokens to reestablish sessions.
On-Path Attacks
Sniffing network traffic.
Unsecured Networks
Public Wi-Fi hotspots.
Malware
Infecting the host to capture cookies.
Cross-Site Scripting (XSS)
Running malicious code in a trusted site or application context.
Session Management
Limit session lifespan, require reauthentication periodically.

What I should remember

Key Points PDF p.361
  • HTTP and Cookies
    • Stateless Protocol: No client information preservation.
    • Cookies: Maintain stateful data.
    • Types: Nonpersistent, persistent.
  • Session Management
    • Session Tokens: Identify and authenticate users.
    • Replay Attack: Capturing or guessing tokens.
  • Capturing Cookies
    • On-Path Attacks: Network sniffing.
    • Unsecured Networks: Public Wi-Fi.
    • Malware: Host infection.
    • XSS: Malicious code in trusted context.
  • Session Prediction Attacks
    • Weaknesses: Token generation algorithms.
    • Requirements: Non-predictable, no revealing information.
    • Management: Limit lifespan, reauthentication.