CWE-210 Base Draft

Self-generated Error Message Containing Sensitive Information

This vulnerability occurs when an application detects a problem and generates its own error messages that accidentally expose sensitive system or user data.

Definition

What is CWE-210?

This vulnerability occurs when an application detects a problem and generates its own error messages that accidentally expose sensitive system or user data.
Instead of using generic, safe error messages, the application crafts detailed responses that can reveal internal information. This might include database structure, server paths, configuration secrets, user credentials, or personal data, giving attackers valuable clues for further exploitation. Developers often create these verbose errors during debugging and forget to replace them before release. To prevent this, always use a centralized, secure logging and error-handling system that separates detailed diagnostic information (for internal logs) from benign, user-facing messages. Never let internal exception details or system information leak to end-users, APIs, or client-side code.
Real-world impact

Real-world CVEs caused by CWE-210

  • CVE-2005-1745

    Infoleak of sensitive information in error message (physical access required).

How attackers exploit it

Step-by-step attacker path

  1. 1

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

  4. 4

    Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable Perl

The following code uses custom configuration files for each user in the application. It checks to see if the file exists on the system before attempting to open and use the file. If the configuration file does not exist, then an error is generated, and the application exits.

Vulnerable Perl 
$uname = GetUserInput("username");
```
# avoid CWE-22, CWE-78, others.* 
  if ($uname !~ /^\w+$/)
  {
  ```
  	ExitError("Bad hacker!") ;
  }
  $filename = "/home/myprog/config/" . $uname . ".txt";
  if (!(-e $filename))
  {
  	ExitError("Error: $filename does not exist");
  }
Secure code example

Secure pseudo

Secure pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist

How to prevent CWE-210

  • Implementation / Build and Compilation Debugging information should not make its way into a production release.
  • Implementation / Build and Compilation Debugging information should not make its way into a production release.
Detection signals

How to detect CWE-210

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

Plexicus auto-fix

Plexicus auto-detects CWE-210 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-210?

This vulnerability occurs when an application detects a problem and generates its own error messages that accidentally expose sensitive system or user data.

How serious is CWE-210?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-210?

MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.

How can I prevent CWE-210?

Debugging information should not make its way into a production release. Debugging information should not make its way into a production release.

How does Plexicus detect and fix CWE-210?

Plexicus's SAST engine matches the data-flow signature for CWE-210 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-210?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/210.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-210

CWE-209 Parent

Generation of Error Message Containing Sensitive Information

This vulnerability occurs when an application reveals sensitive details about its internal systems, user data, or environment within error…

CWE-211 Sibling

Externally-Generated Error Message Containing Sensitive Information

This vulnerability occurs when an application triggers an error message from an external component—like a database, interpreter, or…

CWE-550 Sibling

Server-generated Error Message Containing Sensitive Information

This vulnerability occurs when a web application or server returns detailed error messages that reveal sensitive internal information…

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.

Get started free Book a demo