CWE-535 Variant Incomplete

Exposure of Information Through Shell Error Message

This vulnerability occurs when a web application's command shell returns detailed error messages to users. Attackers can analyze these messages to understand the underlying system, identify…

Definition

What is CWE-535?

This vulnerability occurs when a web application's command shell returns detailed error messages to users. Attackers can analyze these messages to understand the underlying system, identify weaknesses, and potentially gain unauthorized access.
Detailed shell errors, like stack traces or file system paths, act as a roadmap for attackers. They reveal the internal structure of your application, the technologies in use, and sometimes even snippets of code. This information allows an attacker to refine their approach, targeting specific known vulnerabilities in those components or crafting precise injection attacks. Preventing this requires configuring your application to return generic, user-friendly error messages in production, while logging the detailed diagnostics securely for internal review. Managing this at scale across all services is difficult; an ASPM like Plexicus can help you track and remediate these information exposure flaws across your entire stack, using AI to suggest the configuration or code fixes needed to secure error handling.
Real-world impact

Real-world CVEs caused by CWE-535

No public CVE references are linked to this CWE in MITRE's catalog yet.

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 pseudo

MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.

Vulnerable pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
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-535

  • Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
  • Implementation Validate input at trust boundaries; use allowlists, not denylists.
  • Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
  • Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
  • Operation Monitor logs for the runtime signals listed in the next section.
Detection signals

How to detect CWE-535

Automated Static Analysis High

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Plexicus auto-fix

Plexicus auto-detects CWE-535 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-535?

This vulnerability occurs when a web application's command shell returns detailed error messages to users. Attackers can analyze these messages to understand the underlying system, identify weaknesses, and potentially gain unauthorized access.

How serious is CWE-535?

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-535?

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

How can I prevent CWE-535?

Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.

How does Plexicus detect and fix CWE-535?

Plexicus's SAST engine matches the data-flow signature for CWE-535 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-535?

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

Related weaknesses

Weaknesses related to CWE-535

CWE-211 Parent

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-536 Sibling

Servlet Runtime Error Message Containing Sensitive Information

This vulnerability occurs when a Java servlet application displays detailed runtime error messages that reveal sensitive information about…

CWE-537 Sibling

Java Runtime Error Message Containing Sensitive Information

This vulnerability occurs when a Java application's runtime error messages reveal sensitive details about the system, such as file paths,…

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.