Which timing attack exploits side-channel leaks in the browser to estimate the time taken by the browser to process resources?

Which timing attack exploits side-channel leaks in the browser to estimate the time taken by the browser to process resources?

• A. Browser-based Timing Attack
• B. Cookies
• C. CAPTCHA
• D. Direct Timing Attack

Answer: (A)

Timing attacks rely on measuring how long something takes to complete in order to reveal hidden information. In a browser, side-channel leaks can show up as small differences in how long the browser takes to process resources, render pages, or handle scripts. An attacker can tap into these timing differences with high-resolution measurements in JavaScript or from network timings, using them to infer internal processing behavior of the browser or the resources it handles. That environment-specific, measurement-driven leakage is what makes it a browser-based timing attack. Cookies are just data stored by the browser and aren’t used to extract timing information. CAPTCHA is a user-challenge to prove humanity and isn’t about timing side-channels. Direct timing attack is a broader term that isn’t inherently tied to the browser’s environment and its resource processing, whereas the scenario described centers on timing measurements within the browser itself.

Timing attacks rely on measuring how long something takes to complete in order to reveal hidden information. In a browser, side-channel leaks can show up as small differences in how long the browser takes to process resources, render pages, or handle scripts. An attacker can tap into these timing differences with high-resolution measurements in JavaScript or from network timings, using them to infer internal processing behavior of the browser or the resources it handles. That environment-specific, measurement-driven leakage is what makes it a browser-based timing attack.

Cookies are just data stored by the browser and aren’t used to extract timing information. CAPTCHA is a user-challenge to prove humanity and isn’t about timing side-channels. Direct timing attack is a broader term that isn’t inherently tied to the browser’s environment and its resource processing, whereas the scenario described centers on timing measurements within the browser itself.