Improper error handling can lead to which risk?

Improper error handling can lead to which risk?

• A. Improved usability
• B. Faster page loads
• C. Disclosure of sensitive information through error messages
• D. Stronger encryption

Answer: (C)

Improper error handling creates a risk by letting error messages reveal sensitive system details. When an application returns verbose or debugging-friendly errors, it can leak information such as database queries, file paths, stack traces, version numbers, or even partial credentials. An attacker can use that information to map the application, identify weak points, and craft targeted attacks, increasing the likelihood of a breach. The fix is to show generic, non-sensitive messages to users while logging full, secure details on the server for developers. By avoiding disclosure through errors, you reduce the amount of information an attacker can gather. Other options describe outcomes that aren’t risks from error handling—improved usability or faster loads are benefits, and stronger encryption reduces risk rather than creates it.

Improper error handling creates a risk by letting error messages reveal sensitive system details. When an application returns verbose or debugging-friendly errors, it can leak information such as database queries, file paths, stack traces, version numbers, or even partial credentials. An attacker can use that information to map the application, identify weak points, and craft targeted attacks, increasing the likelihood of a breach. The fix is to show generic, non-sensitive messages to users while logging full, secure details on the server for developers. By avoiding disclosure through errors, you reduce the amount of information an attacker can gather.

Other options describe outcomes that aren’t risks from error handling—improved usability or faster loads are benefits, and stronger encryption reduces risk rather than creates it.