<iframe src='https://bank.com'></iframe> <script> const loginform =
window.frames[0].forms[0] loginForm.addEventListener('submit', () => {
console.log(loginForm.username) // Haha, got your username ...
console.lo lo inform. )assword // ...and assword! <Iseri t>
Question 2 f25 Marks]
2.1. An attacker includes the following HTML in their site hosted at https://attacker.com which
makes a GET request to a vulnerable bank server and transfers money into the attacker's
account.
<img src='https://bank.com/withdraw?amount=l 000&to=attacker' />
The attacker is hoping the user is already authenticated with the bank site before they visit
(
https://attacker.com and send the above GET request to the bank. The attacker entices users to
visit their site by including hundreds of cute kittens:
Explain how the bank can modify their server code to protect users from this attack. (5)
2.2. There are two authentication methods in web application session management. Mention
and explain the two methods. (4)
2.3. Differentiate between the two methods mentioned in question 2.2. (4)
2.4. Name and explain 3 security measures can be put in place to ensure that cookies are secured
during communication. (6)
2.5. Mention two attributes that are configured on session cookies and their implications (4)
2.6. Differentiate between authentication and authorisation (2)
(
Question 3 [10]
3.1. Describe a server-side defenses that mitigates the effects of brute force (testing multiple
passwords from a dictionary against a single account), credential stuffing (testing
username/password pairs obtained from a breach), as well as password spraying (testing a
single weak password against a large number of different accounts). (5)
3.2. Suppose an attacker steals the private key of a website that uses TLS and remains
undetected. What can the attacker do using the private key? (4)
3.3. What is security fuzzing? (1)
Page 4 of5