Exam: Chapters 44–53 · Security+ SY0-701

Chapters 44–53 Practice Exam

📝 20 scored questions ⏱️ 30-minute target 🎯 Pass threshold: 80% (16/20)

Time remaining

30:00

Part A — Multiple Choice (Questions 1–20)

Ch 44 · Physical Attacks

Question 1 of 20

An attacker uses a device costing approximately $50 to read and clone an employee's HID proximity access badge from up to 18 inches away in a crowded elevator lobby. The cloned badge successfully opens every door the original badge accesses. No alarms triggered during the cloning operation. Which control would MOST effectively prevent this type of attack from granting unauthorized access to the facility?

A. Replacing HID Prox cards with high-frequency RFID cards that transmit over a shorter range B. Installing CCTV cameras at all card readers to record badge-reading events for later review C. Requiring a second factor — PIN, biometric, or push notification — at access control points in addition to the badge; a cloned badge alone cannot satisfy the second factor D. Restricting badge usage to business hours only to limit the window during which cloning attacks can occur

✅ C. The fundamental weakness of RFID badge-only access is that the badge is a single factor ("something you have") that can be copied. Multi-factor authentication (MFA) requires the attacker to also possess a second factor — a PIN the victim knows, the victim's fingerprint, or a push notification to the victim's phone. Cloning the badge is irrelevant if the cloned badge alone is insufficient for entry. CCTV (B) detects after the fact but doesn't prevent access. Shorter-range cards (A) raise the difficulty but don't eliminate the attack. Business hours restriction (D) doesn't address the core vulnerability — the badge can still be cloned and used during hours.

Ch 44 · Physical Attacks

Question 2 of 20

An attacker, having gained remote access to a data center's building management system via a phishing email, gradually reduces the HVAC cooling output over five hours. Server core temperatures rise until thermal protection circuits trigger automatic shutdown, taking the entire facility offline. How is this attack correctly classified?

A. Denial-of-service via network packet flooding — the HVAC network traffic disrupted server communications B. Environmental attack — targeting physical infrastructure systems (HVAC/cooling) to cause an availability failure; the attacker achieved denial of service without attacking the servers directly C. Physical brute force entry — the attacker broke through physical barriers to reach environmental controls D. Supply chain attack — the HVAC vendor was the compromised party who introduced the vulnerability

✅ B. Environmental attacks target the physical infrastructure that IT systems depend on — power, cooling, humidity, and fire suppression systems. The attacker never touched a server; they attacked the cooling system that servers require to operate. This achieves availability disruption (effectively a DoS) through physical infrastructure rather than network-layer attack. Environmental attacks are particularly dangerous because building management systems are often poorly secured and separated from IT security governance. The defense includes network segmentation of building automation systems, monitoring environmental telemetry, and backup cooling capacity with automated alerts on temperature exceedance.

Ch 45 · Denial of Service

Question 3 of 20

An attacker sends 50-byte UDP queries to thousands of open DNS resolvers with the source IP spoofed as the victim's server address. Each resolver responds with a 4,300-byte DNS response directed at the victim. Using 10,000 resolvers, the attacker generates approximately 86× the traffic volume they injected. The victim's network link is saturated and legitimate users cannot connect. Which attack is described and why are open resolvers effective amplifiers?

A. DNS cache poisoning — the attacker is inserting fraudulent records into resolvers to redirect victim traffic B. DNS amplification DDoS attack — open resolvers respond to any query regardless of source; the asymmetry between small query and large response (86×) is exploited by spoofing the victim's IP as the source, causing resolvers to flood the victim with unsolicited large responses using minimal attacker bandwidth C. Botnet DDoS — the resolvers are compromised botnet nodes receiving C2 commands to attack the victim D. Domain hijacking — the attacker has taken control of the victim's domain records to redirect their traffic

✅ B. DNS amplification uses two properties: (1) UDP source spoofing is possible — UDP does not perform a handshake, so the attacker can set any source IP; (2) DNS responses are significantly larger than queries — especially for ANY or DNSSEC responses, creating amplification factors of 50–100×. The attacker expends 50 bytes of bandwidth to deliver 4,300 bytes to the victim per resolver. Open resolvers (configured to answer queries from any IP) are the involuntary amplifiers. The victim sees traffic from thousands of legitimate DNS server IPs, making source-IP blocking ineffective. Defense: configure DNS servers to reject recursive queries from external sources; ISP-level BCP38 filtering to block spoofed source IPs.

Ch 45 · Denial of Service

Question 4 of 20

What is the PRIMARY operational advantage that makes a DDoS attack harder to defend against than a single-source DoS attack?

A. DDoS attacks target confidentiality; DoS attacks target availability — the different objectives require different defensive tools B. DDoS attacks only exploit application-layer vulnerabilities; DoS attacks rely on bandwidth saturation C. A DDoS uses many distributed source addresses simultaneously, making source-IP blocking ineffective and requiring the defender to absorb or filter traffic across hundreds or thousands of legitimate-looking IPs; a single-source DoS can be blocked with one firewall rule D. DDoS attacks require physical access to the target network; DoS attacks are conducted entirely remotely

✅ C. The core defensive problem with DDoS is the distribution of source addresses. When a single attacker IP is flooding a target, the defender adds one firewall rule blocking that IP. When 100,000 botnet IPs are each sending a moderate stream of traffic, blocking any one source has negligible impact and there are too many to block individually. The attack volume also frequently exceeds the defender's upstream bandwidth capacity — meaning traffic must be mitigated upstream at the ISP level or via a scrubbing service. This is why DDoS defense relies on specialized services (Cloudflare, Akamai) that can absorb and filter traffic at scale rather than simple firewall rules.

Ch 46 · DNS Attacks

Question 5 of 20

A penetration tester with local admin access to a workstation adds the following line to the hosts file: 203.0.113.5 internalbank.corp.com. Users of that workstation who type "internalbank.corp.com" in a browser are now directed to the tester's server. Which DNS attack category does this represent, and why does it bypass the corporate DNS server?

A. DNS server compromise — the tester modified the zone file on the corporate DNS server B. Domain hijacking — the tester changed the registrar account controlling corp.com C. Host file modification — the local operating system consults the hosts file before making DNS queries; an entry in the hosts file takes precedence over DNS server responses, so the DNS server is never asked and its correct answer is never seen D. On-path DNS injection — the tester intercepted DNS query packets in transit and replaced the response

✅ C. The OS hostname resolution order (on Windows and Linux) is: hosts file first, then DNS. If an entry exists in the hosts file for a given hostname, the DNS query is never made. Locations: Windows — C:\Windows\System32\drivers\etc\hosts; Linux/macOS — /etc/hosts. This attack is limited to the local machine (unlike DNS server compromise which would affect all clients) but is effective if the attacker has local admin access. DNSSEC cannot protect against this — it signs DNS responses, but the hosts file bypasses DNS entirely. Defense: monitor hosts file integrity; restrict local admin access; use endpoint security tools that alert on hosts file modifications.

Ch 46 · DNS Attacks

Question 6 of 20

In October 2016, attackers gained control of all 36 domains belonging to a major Brazilian bank for approximately 6 hours by compromising a single account. During that window they controlled DNS records, SSL certificates, email routing, and online banking traffic — redirecting 5 million customers to fraudulent sites. What type of DNS attack does this represent and why was controlling one account sufficient to affect 36 domains?

A. DNS cache poisoning — the attacker injected fraudulent records into the bank's resolvers, affecting all cached lookups B. Domain hijacking via registrar account compromise — all 36 domains were registered under one registrar account; that account functions as a master key granting full control over every domain's DNS records, certificate requests, and configuration C. Typosquatting — the attacker registered look-alike domains for all 36 bank properties and tricked users into visiting them D. BGP hijacking — the attacker announced more-specific routes for the bank's IP blocks, diverting internet traffic at the routing layer

✅ B. Domain hijacking exploits the registrar account as a single point of control for all domains under it. When all domains for an organization are managed under one registrar account, that account grants authority over all zone files, nameserver delegations, and certificate management (via DNS-based DV certificate issuance). Compromising one account with one set of credentials achieved simultaneous control of 36 domains. The defense is multi-factor authentication on registrar accounts, domain registry locking, and separating high-value domains across different accounts or registrars to limit blast radius from a single credential compromise.

Ch 47 · Wireless Attacks

Question 7 of 20

An attacker on a corporate Wi-Fi network uses a script to continuously transmit 802.11 deauthentication management frames targeting all clients associated with the company's access point. Clients disconnect and cannot maintain connections because they are immediately deauthenticated upon reconnecting. Which statement BEST explains the root cause of this attack's effectiveness and the standard technical defense?

A. The attacker exploited a WPA2 encryption weakness that allows unauthenticated modification of the session key; defense: upgrade to WPA3 B. In 802.11 implementations prior to 802.11w, management frames including deauthentication are not cryptographically authenticated — any device with a wireless adapter can forge them using any source MAC address; defense: implement 802.11w (Management Frame Protection), which requires management frames to be cryptographically signed and validated before acting on them C. The attack flooded the AP's processing queue with management frame processing overhead, causing a denial of service; defense: increase access point memory and processing capacity D. Deauth frames exploit the AP's open management port; defense: disable Telnet and SSH on wireless access points

✅ B. In the original 802.11 specification, management frames (deauthentication, disassociation, beacon) were designed without authentication mechanisms. Any device can inject a deauthentication frame with any source MAC address, and clients will honor it — because they have no way to verify whether it came from the legitimate AP or an attacker. 802.11w (Management Frame Protection), ratified in 2009 and incorporated into WPA3, addresses this by requiring unicast management frames to be protected by a shared key derived during the WPA2/3 handshake. Clients and APs supporting 802.11w will only accept signed management frames, ignoring forged ones.

Ch 47 · Wireless Attacks

Question 8 of 20

A security team is tasked with locating an unknown RF transmitter causing 2.4 GHz interference across an office building. They use a directional (Yagi) antenna connected to a spectrum analyzer to identify the signal direction, walk the building's perimeter noting where signal strength peaks, then progressively reduce the apparent signal range by inserting an RF attenuator as they close in on the source — eventually locating a rogue device hidden behind a server rack. What is this methodology called?

A. Wardriving — systematically surveying wireless signals from a vehicle moving through the building's exterior B. Passive RF scanning — using an omnidirectional antenna to map signal levels across the 2.4 GHz spectrum C. Fox hunting (RF direction finding) — using a directional antenna to identify signal bearing combined with signal attenuation to avoid overshooting the source, progressively narrowing the physical search area until the transmitter is located D. Spectrum triangulation via SNMP polling of access point RSSI readings to calculate transmitter coordinates

✅ C. Fox hunting (named after the amateur radio sport "foxhunting" or "ARDF" — Amateur Radio Direction Finding) is the methodology for physically locating a radio transmitter using directional equipment. Key tools: directional antenna (Yagi or similar) to determine bearing to the signal source; attenuator (reduces sensitivity as you get close to avoid the signal overwhelming the detector, which would make it appear to come from everywhere). The technique: sweep direction, find peak signal bearing, move in that direction, use attenuator as signal strengthens to maintain directional sensitivity. This skill is directly applicable to locating rogue access points, RF jammers, and unauthorized transmitters.

Ch 48 · On-Path Attacks

Question 9 of 20

An attacker connected to a switched corporate LAN sends unsolicited ARP reply packets to a victim workstation claiming "the gateway IP 192.168.1.1 is at MAC AA:BB:CC:DD:EE:FF" (the attacker's MAC). The workstation updates its ARP cache and begins forwarding all gateway-bound traffic to the attacker. The attacker forwards traffic normally to prevent detection. Which layer-2 security feature on managed switches would prevent this attack?

A. 802.1X port-based authentication — prevents the attacker from connecting to the switch port at all B. Dynamic ARP Inspection (DAI) — validates each ARP packet against a DHCP snooping binding table mapping IP addresses to MAC addresses and switch ports; ARP replies claiming an IP-to-MAC mapping not in the trusted table are dropped at the switch port before reaching the victim C. VLAN segmentation — places the attacker and victim in different broadcast domains where ARP cannot reach between them D. Port security MAC address limiting — restricts each switch port to one MAC address, preventing the attacker from spoofing the gateway's MAC

✅ B. Dynamic ARP Inspection (DAI) works by maintaining a binding table (populated by DHCP snooping or static entries) that maps IP addresses to their legitimate MAC addresses and switch ports. When an ARP reply arrives, the switch validates the claimed IP-to-MAC mapping against this table before forwarding it. An attacker claiming "192.168.1.1 is at AA:BB:CC:DD:EE:FF" fails the DAI check because the table shows 192.168.1.1 is bound to the gateway's real MAC on the uplink port — not the attacker's MAC on their access port. The frame is dropped. VLAN segmentation (C) limits broadcast domains but doesn't stop ARP spoofing within the same VLAN where attacker and victim coexist.

Ch 48 · On-Path Attacks

Question 10 of 20

A victim's computer has a banking trojan installed that registers itself as a browser helper object. The victim visits their bank's website using HTTPS. The padlock icon shows a valid certificate. Despite HTTPS being intact, the attacker captures the victim's account credentials and modifies the transfer amount before it is submitted. Which explanation BEST describes why HTTPS failed to protect the victim?

A. The attacker broke TLS by finding a collision in the bank's certificate hash, invalidating the HTTPS connection B. The malware replaced the bank's certificate with a fraudulent one and tricked the browser into accepting it C. The on-path browser attack operates inside the browser, above the TLS decryption layer — it reads plaintext content after TLS decryption (before display) and injects content before TLS re-encryption (before transmission); the TLS tunnel between browser and server is intact, but the compromise occurs at the application layer within the browser itself D. HTTPS only encrypts the TCP headers, not the HTTP payload — credentials in POST bodies are never encrypted

✅ C. This is the key insight of on-path browser attacks (also called man-in-the-browser or MitB): the attack does not need to break TLS because it operates on the inside of the TLS endpoint. The browser decrypts TLS data before displaying it and encrypts data before sending it. The malicious browser extension or helper object inserts itself into that process — reading decrypted content from the DOM (document object model) and modifying POST data before the browser re-encrypts it for transmission. From the network's perspective: HTTPS connection is legitimate, certificate is valid, encryption is intact. The bank's servers receive what appears to be a valid, authenticated session. The compromise is invisible to network monitoring. Defense: out-of-band transaction verification (e.g., SMS or app confirmation for transfers).

Ch 49 · Replay Attacks

Question 11 of 20

An attacker compromises a Windows workstation and uses a credential dumping tool to extract NTLM password hashes from LSASS memory. Without ever cracking or reversing the hashes, the attacker successfully authenticates to a file server and a domain controller using the extracted hash values directly. Which attack is described and what property of the NTLM authentication protocol makes this possible?

A. Offline brute force — NTLM hashes are weakly constructed and can be reversed to plaintext in seconds using GPU cracking before re-authentication B. Pass-the-hash — in NTLM's challenge-response authentication protocol, the client responds to the server's challenge by computing a value using the NT hash directly; the server accepts the correctly computed response without the client ever needing to know the plaintext password; possessing the hash is functionally equivalent to possessing the password C. Kerberos golden ticket attack — the attacker forged a Kerberos TGT using the extracted hash as the krbtgt key D. Session replay — the attacker captured and replayed a previously observed valid authentication packet

✅ B. Pass-the-hash is possible because NTLM uses a challenge-response protocol where the authentication proof is computed from the NT hash, not the plaintext password. The server sends a random challenge; the client responds with HMAC-MD5(NT_hash, challenge). If you have the NT hash, you can compute the correct response — the plaintext password is never needed. This makes NTLM fundamentally vulnerable to credential reuse: obtaining the hash from one system grants access to any other system where the same credentials are valid, without ever cracking the password. Defense: Kerberos (which uses tickets and temporal nonces, not replayable hashes); Protected Users group; Credential Guard (which prevents hash extraction from LSASS).

Ch 49 · Replay Attacks

Question 12 of 20

The Firesheep Firefox extension (released October 2010) allowed non-technical users at coffee shops to click a button and instantly take over the Facebook, Twitter, or Amazon sessions of others on the same Wi-Fi network. Which vulnerability did it exploit, and which combination of controls would prevent this attack?

A. WPA2 key recovery — Firesheep captured the Wi-Fi PSK and decrypted all traffic; defense: use WPA3-SAE B. Session cookie hijacking via packet capture on unencrypted HTTP — Firesheep sniffed session cookies transmitted in plaintext on the shared broadcast wireless medium and replayed them to impersonate the victim; defense: HTTPOnly + Secure cookie flags (prevent cookie transmission over HTTP) and site-wide HSTS (force HTTPS for all traffic including session cookies) C. ARP poisoning — Firesheep redirected Wi-Fi traffic through the attacker's interface using spoofed ARP replies; defense: DAI on the access point D. DNS cache poisoning — Firesheep modified local DNS caches to redirect social media site requests; defense: DNSSEC

✅ B. Firesheep exploited the fact that many major websites in 2010 performed their login pages over HTTPS but then issued session cookies without the Secure flag and transmitted subsequent pages over HTTP. On an open Wi-Fi network (shared broadcast medium), all HTTP traffic is visible to any device in passive listening mode. Firesheep simply captured these unencrypted session cookies from the Wi-Fi broadcast and replayed them. The Secure cookie flag instructs browsers to never transmit a cookie over HTTP, only HTTPS. HSTS ensures HTTPS is always used. Together, they ensure session cookies are never transmitted in a form capturable by passive sniffing. Firesheep's release forced major sites to implement site-wide HTTPS for session management, accelerating HTTPS adoption industry-wide.

Ch 50 · Malicious Code

Question 13 of 20

WannaCry (May 12, 2017) infected approximately 230,000 systems across 150 countries in a single day. The malware encrypted victim files and demanded Bitcoin payment. It spread autonomously across networks without any user interaction. The NSA had discovered the underlying vulnerability years earlier. A security researcher stopped the global outbreak by registering a domain name for $10.69. Which combination of malware categories BEST classifies WannaCry, and what was the kill switch mechanism?

A. Virus and spyware — it spread by attaching to executable files and silently exfiltrated files to attacker servers; the kill switch was a firewall rule blocking its C2 server B. Ransomware and worm — it encrypted files and demanded ransom (ransomware) and self-propagated via the EternalBlue SMB exploit without user interaction (worm); before encrypting, the malware queried a specific unregistered domain — if the domain resolved (returned any response), the malware exited; registering the domain caused all running instances to stop C. Trojan and keylogger — it disguised itself as a Windows update and captured credentials before deploying ransomware; the kill switch was a code signature that Microsoft deployed via Windows Defender D. Logic bomb and rootkit — it was pre-installed on systems via compromised supply chain and activated on a specific date; the kill switch was a time condition embedded in the logic bomb trigger

✅ B. WannaCry = ransomware (encrypts files, demands payment) + worm (EternalBlue/MS17-010 SMB exploit for autonomous propagation — no user needed to open a file). The kill switch was an anti-analysis artifact: malware authors sometimes check whether a specific domain resolves as a sandbox detection mechanism (sandboxes often resolve all domains). The researcher Marcus Hutchins registered the domain (iuqerfsodp9ifjaposdfjhgosurijfaewrwergwea.com) for $10.69 — once it resolved, the malware's check returned "domain exists → exit." The underlying exploit, EternalBlue, exploited CVE-2017-0144 in Windows SMBv1 — patched by Microsoft in March 2017 (MS17-010) before WannaCry, but millions of systems remained unpatched when the attack occurred in May 2017.

Ch 50 · Malicious Code

Question 14 of 20

In 2018, attackers compromised the British Airways website and injected 22 lines of JavaScript into the payment checkout page. For two weeks, every customer entering payment details had their card number, CVV, and billing address silently exfiltrated to an attacker-controlled server — simultaneously with the legitimate payment completing. Approximately 380,000 customers were affected and British Airways received a £20M GDPR fine. What web attack technique does this represent?

A. Stored XSS — the attacker stored a persistent malicious script in the BA database that was served to all visitors B. SQL injection — the attacker exfiltrated stored payment card data directly from BA's payment database C. Formjacking (Magecart attack) — malicious JavaScript injected into the payment form intercepts the form submission event and copies entered data to an attacker server before (or alongside) the legitimate payment processor; no stored data needed — the attack captures live input D. CSRF — the attacker forged authenticated payment requests from victims' browsers to transfer funds to attacker-controlled accounts

✅ C. Formjacking (also called a Magecart attack after the criminal group that pioneered it at scale) injects malicious JavaScript into e-commerce payment forms. When the victim types card data and submits the form, the injected script fires first — copying all field values to an attacker-controlled endpoint. The legitimate payment also completes, so the victim has no indication anything was wrong. Unlike SQL injection (B), no stored database is accessed. Unlike XSS (A), the goal isn't browser script execution for other purposes — it's specifically the skimming of form data. This attack targets the client side, meaning server-side security (WAF, database controls) provides no protection; Content Security Policy (CSP) restricting which domains JavaScript can phone home to is the primary technical defense.

Ch 51 · Application Attacks

Question 15 of 20

An application's login query is: SELECT * FROM users WHERE username='[INPUT]' AND password='[INPUT]'. An attacker enters admin'-- as the username and any string as the password. The resulting query is: SELECT * FROM users WHERE username='admin'--' AND password='anything'. The attacker is authenticated as admin. Which vulnerability enables this attack and what is the complete, correct remediation?

A. Buffer overflow — the single quote character overflows the string buffer; defense: validate input length before processing B. Cross-site scripting — the quote character triggers HTML context switching in the database rendering engine; defense: output encoding C. SQL injection (authentication bypass) — the single quote closes the string literal in the SQL syntax; -- is the SQL comment operator, causing the database parser to discard everything after it (including the password check); defense: parameterized queries (prepared statements), which send query structure and user data separately so user input can never be parsed as SQL syntax D. Path traversal — the attacker navigated up the database structure using the ' character; defense: canonical path normalization at the database layer

✅ C. SQL injection occurs when user input is concatenated directly into a SQL statement, allowing the user to inject SQL syntax. Here: (1) the single quote (') closes the string literal that started with username='; (2) -- comments out the rest of the line, eliminating the password check entirely. The database executes: SELECT * FROM users WHERE username='admin' — which returns the admin record with no password verification. The fix is parameterized queries: the query structure is fixed (e.g., SELECT * FROM users WHERE username=? AND password=?), and user input is passed as bound parameters. The database driver ensures parameters are treated as data values, never as SQL syntax — the single quote in admin'-- becomes a literal character search, not a string delimiter.

Ch 51 · Application Attacks

Question 16 of 20

A victim is authenticated to their bank. They visit a forum that contains a hidden image tag: <img src="https://bank.com/transfer?to=attacker&amount=5000" style="display:none">. Their browser automatically sends a GET request to that URL, including their bank session cookie. The transfer completes successfully. The victim authorized nothing. Which attack is described and what server-side control specifically prevents it?

A. XSS — the attacker injected script into the bank's page that executed under the bank's origin; defense: Content Security Policy headers B. Session hijacking — the attacker stole and reused the victim's session cookie; defense: HTTPOnly flag on cookies C. CSRF (Cross-Site Request Forgery) — the browser automatically includes session cookies with any request to bank.com regardless of which site triggered it; the bank processed the forged request as legitimate because it came with valid cookies; defense: anti-CSRF token — a unique unpredictable value embedded in every state-changing form, validated server-side; an attacker cannot include a valid token they've never seen D. Clickjacking — the forum page overlaid a transparent bank UI that the victim unknowingly clicked; defense: X-Frame-Options header

✅ C. CSRF exploits the browser's automatic inclusion of cookies with requests. The victim's browser holds a valid bank session cookie. When the forum page's image tag triggers a GET to bank.com, the browser automatically attaches the session cookie — authenticating the request as the victim. The bank server sees a valid, authenticated request and executes the transfer. The anti-CSRF token breaks this: each form includes a cryptographically random, per-session token. The server validates the token on submission. An attacker on a different origin cannot read the victim's token (same-origin policy prevents cross-origin JavaScript from reading page content) and therefore cannot forge a valid request. Note: for this attack, the action was triggered via GET (poor practice); state-changing operations should use POST with anti-CSRF tokens, and SameSite=Strict cookie attribute also mitigates CSRF.

Ch 52 · Cryptographic Attacks

Question 17 of 20

SHA-1 has a 160-bit output, which would suggest 2¹⁶⁰ operations needed to find any two inputs with the same hash. The SHAttered attack (2017) found a practical collision using approximately 2⁶³ operations — about 100 quadrillion times fewer. SHA-256 provides 128-bit collision resistance despite its 256-bit output. What principle explains why collision resistance is half the output size in bits?

A. Pre-image resistance degradation — SHA algorithms have a structural flaw that reduces effective output strength by half B. The birthday bound — finding any collision between two inputs requires only approximately √N operations for a hash with N possible outputs; a 256-bit hash has 2²⁵⁶ possible outputs, so the birthday attack requires ~2¹²⁸ operations (256/2 bits), not 2²⁵⁶; this halving applies to any hash algorithm regardless of structural design C. SHA algorithms use a 128-bit internal compression state regardless of output length, capping actual collision resistance at 2⁶⁴ D. Collision resistance and pre-image resistance are identical properties — both require 2^N operations for an N-bit hash

✅ B. The birthday bound is the fundamental reason collision resistance is half the output bit length. The birthday paradox states that finding any two matching values from a set of N possibilities requires only √N trials. √(2²⁵⁶) = 2¹²⁸. This is a mathematical property of probability — not a design flaw in any specific algorithm. The insight is "any two" rather than "a specific one": there are n(n-1)/2 pairs to check among n trials, so collisions become probable when n ≈ √N. SHA-256's defense against birthday attacks is the 256-bit output giving 128-bit collision resistance — computationally infeasible. SHA-1's birthday bound of 2⁸⁰ was theoretically breakable, and structural weaknesses in SHA-1's design allowed SHAttered to achieve it at 2⁶³.

Ch 52 · Cryptographic Attacks

Question 18 of 20

A security architect configures a web server to reject all connections using SSL 3.0, TLS 1.0, and TLS 1.1, supporting only TLS 1.2 and TLS 1.3. Which attack does this configuration specifically prevent, and what is the mechanism by which removing legacy protocol support provides protection?

A. SSL stripping — removing legacy protocols forces clients to connect via HTTPS; without HTTP fallback, SSL stripping cannot intercept the connection B. Birthday attacks against MD5-signed certificates — TLS 1.0 and 1.1 allow MD5 certificate signatures; removing them prevents hash collision-based certificate forgery C. POODLE and TLS downgrade attacks — an on-path attacker forces downgrade by injecting errors into TLS 1.2/1.3 handshakes, hoping the client falls back to a legacy version; with no legacy versions available on the server, the handshake fails completely rather than downgrading, and the SSL 3.0 CBC padding oracle vulnerability is unreachable D. Pass-the-hash attacks — legacy TLS versions transmitted NTLM hashes without encryption; TLS 1.3 encrypts all handshake data including credential exchanges

✅ C. POODLE (Padding Oracle On Downgraded Legacy Encryption) requires two phases: first, downgrade the TLS connection to SSL 3.0 (by injecting errors that cause successive TLS version failures); second, exploit SSL 3.0's CBC mode padding oracle. If the server has no SSL 3.0 or legacy TLS support, the downgrade has no destination — the connection fails rather than succeeding on a vulnerable protocol. The padding oracle in SSL 3.0 is then unreachable. This is an implementation attack (the TLS algorithm isn't broken; the fallback configuration was vulnerable) requiring an implementation fix (remove the fallback target). SSL stripping (A) is addressed by HSTS — not by disabling legacy TLS versions; those are independent issues.

Ch 53 · Password Attacks

Question 19 of 20

Authentication logs for a corporate VPN show that between 2:00 AM and 3:00 AM, 643 accounts each received exactly two failed login attempts using the passwords "Welcome1" and "CompanyName2024". No account was locked out. The VPN's account lockout policy triggers after 5 consecutive failures. Which attack occurred and what is the most effective single control to mitigate it?

A. Online brute force — the attacker ran a dictionary attack against individual accounts; the lockout policy should be reduced from 5 to 3 attempts B. Offline brute force — the attacker obtained the VPN's hash file and tested password hashes locally against it; defense: bcrypt hashing C. Password spraying — the attacker tested a few common/organization-predictable passwords across all accounts, keeping each account at exactly 2 attempts — well below the 5-attempt lockout threshold; the most effective control is MFA, which renders a correctly guessed password alone insufficient for VPN access D. Credential stuffing — the attacker used username-password pairs from prior breaches; defense: check credentials against breach databases

✅ C. Password spraying's defining signature is exactly what the logs show: many accounts, few attempts each, same password(s) — and no lockouts. "Welcome1" and "CompanyName2024" are textbook spray targets: the first is a generic workplace-welcome pattern; the second is an organization-name + year pattern, extremely common as a "meets complexity requirements" password choice. The attack is specifically designed to stay below the lockout threshold — reducing the threshold to 3 (instead of 5) would just force the attacker to use 2 attempts instead of more. MFA is the correct control: even if one of 643 accounts uses "Welcome1" and the attacker finds it, they still cannot authenticate without the second factor the attacker doesn't possess.

Ch 53 · Password Attacks

Question 20 of 20

A web application's password database is breached. Passwords were stored as SHA-256 hashes without salting. An attacker using a GPU cluster cracks 60% of accounts within 4 hours, including many that shared the same password (cracked once, applied to all identical hashes). The security team proposes the following fixes: (I) add account lockout to the login page; (II) switch to bcrypt with per-user salting. Which proposal(s) correctly address the demonstrated vulnerability and why?

A. Proposal I only — account lockout prevents the attacker from using cracked credentials to log in, blocking the impact of the breach B. Proposal II only — the attack was an offline brute force that never contacted the authentication endpoint; account lockout has zero effect on offline cracking; bcrypt slows per-hash computation by orders of magnitude; salting prevents rainbow table lookups and forces per-account cracking C. Both proposals — account lockout stops the online attack phase; bcrypt and salting stop the offline phase; together they provide complete protection D. Neither — the only correct fix is preventing database breaches through better access controls; hashing algorithm choice does not affect the attacker's ability to crack passwords once the file is obtained

✅ B. This is a critical exam distinction. The demonstrated attack was offline brute force — the attacker ran cracking tools against the downloaded hash file. Account lockout (I) applies to the live authentication endpoint; the cracking phase never made a single login attempt — there is nothing to lock out. Adding lockout to the login page does nothing to stop an attacker who already has the hash file and is cracking it locally. Bcrypt (II) addresses the attack directly: SHA-256 evaluates at ~10 billion hashes/second per GPU; bcrypt (cost 12) evaluates at ~20,000/second — a 500,000× slowdown that makes the 60%-in-4-hours result impossible. Per-user salting prevents identical-password batch cracking (one crack doesn't apply to all accounts with the same password) and defeats rainbow table lookups. These two controls target the offline cracking capability itself.

Part B — Scenario Analysis (Unscored — for practice)

Ch 44–49 · Scenario

Scenario A — Multi-Stage Network Attack Classification

A security team investigates a serious incident at a financial services firm. The timeline shows: (1) An on-path attacker on the corporate LAN sent forged ARP replies claiming the gateway's IP belonged to the attacker's MAC, redirecting all employee traffic through the attacker's machine. (2) During this interception, the attacker captured session cookies for the HR portal — which used HTTP for session management. (3) Using these cookies, the attacker accessed the HR portal without credentials, changed bank routing information for payroll, and exfiltrated employee records. (4) A separate investigation reveals an IT admin's Active Directory credentials were stolen via pass-the-hash — their NTLM hash was extracted from a compromised workstation and used to authenticate to the domain controller without ever cracking it. Classify each stage of the attack, identify the vulnerable design decision that enabled each, and specify the exact technical control that would have prevented each stage.

Stage 1 — ARP Poisoning (On-Path Attack):
Classification: ARP poisoning / on-path attack at Layer 2. The attacker exploited the lack of ARP validation — ARP has no authentication; any device can claim any IP-to-MAC mapping.
Vulnerable design: No Dynamic ARP Inspection (DAI) on the managed switch.
Control: DAI validates ARP packets against the DHCP snooping binding table. An ARP reply claiming the gateway IP with a non-gateway MAC would be dropped at the switch port before reaching any endpoint. This single control stops ARP poisoning entirely on a managed switch.

Stage 2 — Session Cookie Capture:
Classification: Session hijacking / replay attack. Once on-path, the attacker captured plaintext session cookies from HTTP traffic.
Vulnerable design: The HR portal issued session cookies without the Secure flag (allowing HTTP transmission) and did not enforce HTTPS for authenticated sessions.
Control: (1) Secure cookie flag — instructs browsers to never send the cookie over HTTP; (2) HTTPOnly flag — prevents JavaScript access; (3) HSTS — enforces HTTPS for all communication, so even if ARP poisoning succeeds, the attacker sees only encrypted HTTPS traffic and cannot read session cookies from it. Note: if stage 1 (ARP poisoning) is prevented, stage 2 becomes impossible anyway. Defense in depth means each stage has an independent control.

Stage 3 — Unauthorized HR Portal Access:
Classification: Session replay attack using hijacked credentials (the captured session cookie). The attacker used a valid cookie to impersonate an authenticated employee.
Vulnerable design: Session cookies had no binding to IP address or user-agent; the cookie was sufficient alone for authentication with no secondary factor.
Control: Beyond cookie security, adding MFA at the HR portal for sensitive actions (payroll routing changes, bulk data exports) would have required the attacker to have a second factor they lacked. Activity monitoring — alerts on bulk data exports or payroll routing changes — would have detected the anomalous access regardless of authentication method.

Stage 4 — Pass-the-Hash Domain Controller Access:
Classification: Pass-the-hash attack. NTLM authentication accepts the hash directly as proof of identity — the attacker never needed the plaintext password.
Vulnerable design: (1) NTLM authentication still enabled on the domain controller; (2) LSASS credential storage not protected against memory scraping; (3) admin account used for day-to-day workstation activity, leaving hashes cached on endpoints.
Controls: (1) Credential Guard — isolates LSASS in a virtualized secure container; credential dumping tools cannot read credentials from it; (2) Protected Users security group — prevents NTLM authentication for group members (forces Kerberos, which uses time-limited tickets with nonces rather than replayable hashes); (3) Privileged Access Workstations (PAW) — admin accounts should only be used on hardened, dedicated machines, not general-purpose workstations where malware can dump their hashes; (4) Disable NTLM authentication domain-wide where Kerberos is available.

Ch 50–53 · Scenario

Scenario B — Cryptographic and Password Security Audit

A security auditor reviews a company's authentication and cryptographic posture and finds three issues: (1) The company's document management system signs contracts using MD5 as the hash algorithm before applying RSA-2048 signatures. (2) The public-facing web portal redirects HTTP to HTTPS via a 301 response, but has no HSTS header; a demo shows an attacker on the same Wi-Fi network can capture employee credentials in plaintext. (3) The employee portal's password database uses SHA-256 without salting. After a simulated breach of the password table, a GPU cluster cracks 55% of passwords in 3 hours, and all 47 accounts using the same password ("Welcome1") are cracked simultaneously from a single hash computation. For each finding, state the attack it enables, classify it as an algorithm attack or implementation attack, and provide the precise remediation.

Finding 1 — MD5 Document Signing:
Attack enabled: Birthday attack / hash collision. An attacker can engineer two documents with the same MD5 hash (practical since 2004). Having an authorized party sign the legitimate document, the attacker substitutes the fraudulent one — the RSA-2048 signature validates on the fraudulent document because both share the same MD5 digest. RSA-2048 is not involved in the vulnerability; the weakness is entirely in the hash algorithm.
Classification: Algorithm attack. MD5's collision vulnerability is in its mathematical design. Any correct implementation of MD5 is vulnerable — the issue is the algorithm choice, not the configuration.
Remediation: Replace MD5 with SHA-256 in the signature algorithm (SHA-256withRSA). SHA-256 provides 2¹²⁸ birthday-bound collision resistance — computationally infeasible. Re-sign any high-value existing contracts with SHA-256 where legally required.

Finding 2 — HTTP to HTTPS Redirect Without HSTS:
Attack enabled: SSL stripping. An on-path attacker intercepts the 301 redirect before it reaches the browser. The victim's browser never learns HTTPS exists; stays on HTTP; transmits credentials in plaintext. The attacker maintains HTTPS with the server. No browser warning appears. The demo confirms this works despite HTTPS being configured.
Classification: Implementation attack. HTTPS is correctly configured on the server. TLS is not broken. The 301 redirect is a server response that can be intercepted. The deployment is vulnerable because HSTS (which makes HTTPS enforcement browser-side, before any HTTP request is sent) was not implemented.
Remediation: Add the HSTS header to all HTTPS responses: Strict-Transport-Security: max-age=31536000; includeSubDomains. After browsers store this policy, they refuse to send any HTTP request to the domain — SSL stripping has nothing to intercept. For maximum protection: submit to the HSTS preload list (ships the policy in the browser, protecting first-time visitors before they've ever received the HSTS header).

Finding 3 — SHA-256 Without Salting:
Attack enabled: Two simultaneous vulnerabilities: (a) Offline brute force at GPU speed — SHA-256 evaluates at ~10 billion hashes/second; 55% cracked in 3 hours demonstrates the speed advantage over slow-hash algorithms like bcrypt. (b) Batch cracking of identical passwords — without salting, all 47 accounts using "Welcome1" store the same hash; cracking it once reveals all 47 passwords simultaneously, multiplying the attacker's return per cracking computation.
Classification: Implementation attack. SHA-256 is a sound cryptographic algorithm — but it is designed for speed (cryptographic agility, code signing, data integrity). For password storage, speed is a liability; an attacker benefits from the same speed. Using SHA-256 for passwords without salting is a deployment choice, not an algorithm flaw.
Remediation: (1) Replace SHA-256 with bcrypt (cost ≥ 12) or Argon2id — algorithms designed to be computationally expensive per hash (~50ms per attempt vs. ~0.0001ms for SHA-256); this reduces GPU cracking from billions/second to thousands/second. (2) Add per-user random salting — unique salt generated for each user, stored alongside the hash; identical passwords produce different hashes; rainbow tables are useless; batch cracking is eliminated — each account must be attacked individually. Both controls are required together; bcrypt already includes internal salting, making it the single recommended choice for new implementations.

← Exam: Ch 40–43 All Chapters

—

Pass threshold: 80% (16 / 20 correct)

← Ch 40–43 Exam All Chapters

Exam: Attack Techniques