Chapter 6 · Reading 3 of 6
Authentication Attacks
Security+ SY0-801 · Objectives 4.5
A student signs out on a shared computer. The next person uses the browser’s back button and sees a reservation summary. Is this a still-valid session, a cached page or a fresh authorized response? The remedy depends on the answer.
Password authentication attacks involve attempts to steal or guess a user's password to gain unauthorized access to a system. Common methods include brute force attacks, where attackers try every possible password combination, and credential stuffing, where attackers use lists of stolen username-password pairs from previous breaches to access multiple accounts.
Session attacks, such as session hijacking, involve intercepting or stealing a user's session token to impersonate them on a network. This can lead to unauthorized access to sensitive information and services.
Cookie stealing and manipulation involve capturing and altering cookies that store session data. Attackers can hijack a user's session by stealing their cookies or manipulate cookies to gain unauthorized access.
Unvalidated redirects occur when a web application redirects users to another URL without validating the destination. Attackers can exploit this to redirect users to malicious sites.
Insecure Direct Object References (IDOR) happen when an application exposes internal objects through URLs or parameters without proper authorization checks, allowing attackers to access unauthorized data.
Directory traversal attacks enable attackers to access restricted directories and execute commands outside the web server's root directory. This can expose sensitive files and system configurations.
File inclusion vulnerabilities, such as Remote File Inclusion (RFI) and Local File Inclusion (LFI), allow attackers to include external or local files in a web application, potentially executing malicious code.
Privilege escalation occurs when attackers exploit vulnerabilities to gain higher-level permissions than intended, allowing them to perform unauthorized actions, such as accessing sensitive data or executing privileged commands.
Closing active sessions
A changed password may leave an existing session token usable. Check whether the application revokes active sessions, refresh credentials and remembered devices when responding to a compromised account. Reauthenticate before sensitive changes and enforce inactivity and absolute timeouts on the server.
Walk through sign-out from both ends
Use two synthetic accounts and record what the browser displays before and after sign-out. Check whether a new protected request reaches the service and which identity, if any, the service accepts. A cached screen can disclose information even after server-side access has been revoked. Conversely, hiding the screen can leave a valid credential available to make further requests.
Trace password recovery and sign-out across each relying application. Ask how long an existing session remains usable, whether a sensitive action requires fresh authentication and who can invalidate compromised sessions. Write a finding that distinguishes observed data exposure from continued permission to change a booking. That distinction gives the application owner a much more precise fix.
Inspect the three records, then use the evidence to answer the question.
1. Sign in
Establish the user’s identity.
Portal issued a session at 09:00
2. Session
Associate later requests with that identity.
Absolute lifetime is 30 minutes
3. Resource check
Verify permission for this specific record.
User made a request at 09:28
Apply the reading
A student signs in successfully and requests a different student’s transcript. Which decision should the service make next?
Compare your reasoning
Check whether this identity may read that particular transcript. A valid session alone establishes no such permission.