CWE-56 Variant Incomplete

Path Equivalence: 'filedir*' (Wildcard)

This vulnerability occurs when an application accepts file or directory paths containing an asterisk wildcard ('*') without proper validation. Attackers can exploit this to bypass intended access…

Definition

What is CWE-56?

This vulnerability occurs when an application accepts file or directory paths containing an asterisk wildcard ('*') without proper validation. Attackers can exploit this to bypass intended access controls, potentially reading, writing, or executing files in unauthorized locations.
The core issue is that the asterisk wildcard, often used for pattern matching, is interpreted by the underlying operating system during path resolution. When an application passes user-supplied input like 'config*.txt' directly to file system APIs, the OS may resolve it to multiple unexpected files (e.g., 'config.txt', 'config_backup.txt', 'config_old.txt'). This creates an ambiguous path that can lead to unauthorized data exposure, file corruption, or even remote code execution if critical system files are targeted. To prevent this, developers must implement strict input validation that rejects paths containing wildcards before processing. Alternatively, applications should use allowlists of permitted filenames or canonicalize the path and then verify it resides strictly within the intended directory. Never rely on client-side validation alone; all path sanitization must be performed server-side using the application's trusted context.
Real-world impact

Real-world CVEs caused by CWE-56

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-56

  • Implementation Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
Detection signals

How to detect CWE-56

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

This vulnerability occurs when an application accepts file or directory paths containing an asterisk wildcard ('*') without proper validation. Attackers can exploit this to bypass intended access controls, potentially reading, writing, or executing files in unauthorized locations.

How serious is CWE-56?

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

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

How can I prevent CWE-56?

Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.

How does Plexicus detect and fix CWE-56?

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

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

Related weaknesses

Weaknesses related to CWE-56

CWE-41 Parent

Improper Resolution of Path Equivalence

This vulnerability occurs when an application fails to properly handle different text representations that refer to the same file or…

CWE-42 Sibling

Path Equivalence: 'filename.' (Trailing Dot)

This vulnerability occurs when a system accepts file or directory paths that end with a dot (like 'file.txt.' or 'folder.') without…

CWE-44 Sibling

Path Equivalence: 'file.name' (Internal Dot)

This vulnerability occurs when an application accepts file paths containing internal dots (like 'file.ordir') without properly checking…

CWE-46 Sibling

Path Equivalence: 'filename ' (Trailing Space)

This vulnerability occurs when an application processes file paths that end with a space character (like 'document.txt ') without properly…

CWE-47 Sibling

Path Equivalence: ' filename' (Leading Space)

This vulnerability occurs when an application accepts file or directory paths that begin with a space character (like ' filename'),…

CWE-48 Sibling

Path Equivalence: 'file name' (Internal Whitespace)

This vulnerability occurs when an application accepts file paths containing internal spaces (like 'file name') without proper validation.…

CWE-49 Sibling

Path Equivalence: 'filename/' (Trailing Slash)

This vulnerability occurs when an application accepts file or directory paths that end with a slash (e.g., 'documents/') without properly…

CWE-50 Sibling

Path Equivalence: '//multiple/leading/slash'

This vulnerability occurs when an application accepts file or directory paths containing multiple leading slashes (like…

CWE-51 Sibling

Path Equivalence: '/multiple//internal/slash'

This vulnerability occurs when an application accepts file or directory paths containing multiple consecutive forward slashes (e.g.,…

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.