Verbose error messages meaning, in plain words

Verbose error messages show internal details on an error screen. How it works, why it helps attackers, and how to limit what is shown, per MITRE CWE and OWASP.

Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated

Verbose error messages means internal information is shown on an error screen. MITRE's CWE-209 defines it as the weakness of generating error messages that contain sensitive information about the environment, the users, or related data.

How do verbose error messages work?

Picture asking a post office counter why a parcel could not be delivered, and being handed the office's internal floor plan and the staff list as well. The person asking does not need it, and it gives a person with bad intent a lead.

When a program reaches an unexpected state, an error showing the cause appears on screen. That is handy during development, but if it is published as it is, the names and versions of the software in use, file locations, and the content of queries to the database become visible from outside. OWASP's error handling cheat sheet explains that such implementation details make it easier for an attacker to plan the next step. A specific example is on the information disclosure page.

Why do verbose error messages matter?

In preparing an attack, an error screen can serve as research material. If the software version is known, it is easier to target a vulnerability published for that version. Even if the site itself has no hole, the information is handed over first.

MITRE's CWE-209 measure is to narrow what is shown to what the reader needs. Detailed content goes to the log, and sensitive information such as passwords is kept out of the log too. To the same input mistake, answer with the same wording, so that internal states such as whether an account exists are not revealed.

OWASP advises returning a simple notice without implementation details for unexpected errors, and recording the details on the server. In a production environment, set it not to output debugging information. Turning off PHP's display_errors also appears as an example in CWE-209. The operating side also decides where logs are kept and who may view them.

To go over what your error screens show, contact us.

Related terms

  • Vulnerability: a weakness in a program or setting that can become an entry for attack.
  • Audit log: a record for checking later who did what.
  • Debug mode enabled: development features left on in production.
  • Information disclosure: a flaw where internal information not meant to be shown becomes visible from outside.

Next step

The full range of information that must not be shown is on the information disclosure page. The free URL check shows only what is visible from outside. If you want your error screens reviewed, contact us.

Frequently asked questions

What on an error screen makes it too detailed?

Names and versions of the software in use, the locations of files on the server, and the content of queries to the database. OWASP also advises not showing such implementation details.

If we hide error details, will we lose track of the cause of a fault?

Show users only a short notice, and keep the details in server-side logs. Only the operating side views the details. Decide in advance where the logs are kept and who can see them.

Frequently asked questions

What on an error screen makes it too detailed?

Names and versions of the software in use, the locations of files on the server, and the content of queries to the database. OWASP also advises not showing such implementation details.

If we hide error details, will we lose track of the cause of a fault?

Show users only a short notice, and keep the details in server-side logs. Only the operating side views the details. Decide in advance where the logs are kept and who can see them.

See what an attacker can see, today

The free URL check returns a grade in under a minute. For costs and next steps, book a free consultation.