Replay attacks, Application Attack

Question 1

Replay attacks

Answer 1

Attacker captures a transaction message, then replays exact transaction to potentially transfer funds multiple times w/o user’s consent.

Question 2

How do we avoid a replay attack?

Answer 2

Use a session ID w/ a password hash to create a unique authentication hash each time.

Question 3

Session hijacking (Side jacking)

Answer 3

Manipulating a session token, attacker impersonates user and access their data or perform actions w/o authorization.

Question 4

How do we prevent session hijacking?

Answer 4

Encrypt end-to-end
Encrypt end-to-somewhere; personal VPN, avoid capture over local wireless network.

Question 5

Horizontal privilege escalation

Answer 5

Gain higher level access to a system.
User A can access User B resources.
*must be prioritized to patched

Question 6

Injection attacks are enabled because of-

Answer 6

Bad programming, app should properly handle input & output.

Question 7

To solve buffer overflows (not a simple exploit) , developers need to-

Answer 7

Perform bound checking, attackers spend a lot of time looking for openings.

Question 8

Website pages consist of-

Answer 8

Client-side code, Server-side code

Question 9

Client side

Answer 9

Renders page on screen
HTML, JavaScript

Question 10

Server side

Answer 10

-Performs request from client, transfers money from one account to another, post a vid on YT.
-HTML, PHP

Question 11

Cross-site request forgery

Answer 11

Takes advantage of trust that a web app has for the user.

Question 12

What actions can be taken upon to avoid cross-site forgery?

Answer 12

-App should have anti-forgery techniques added
-Usually a cryptographic token to prevent a forgery.