CWE-214 Base Incomplete

Invocation of Process Using Visible Sensitive Information

This vulnerability occurs when a process is started with sensitive data, such as passwords or API keys, passed directly in its command-line arguments or environment variables. Because this…

Definition

What is CWE-214?

This vulnerability occurs when a process is started with sensitive data, such as passwords or API keys, passed directly in its command-line arguments or environment variables. Because this information is often visible to other processes on the system, it can be easily exposed.
On most operating systems, other users can list running processes and view details like command-line arguments and environment variables. If your application launches a subprocess using visible sensitive information, any user with basic system privileges could potentially see those credentials, creating a significant information leak. This exposure allows attackers to directly harvest secrets or understand your application's internal configuration, which can be the first step in a broader attack. To prevent this, sensitive data should never be passed via these visible channels; instead, use more secure methods like pipes, protected files, or inter-process communication (IPC) mechanisms designed to handle secrets.
Real-world impact

Real-world CVEs caused by CWE-214

  • CVE-2005-1387

    password passed on command line

  • CVE-2005-2291

    password passed on command line

  • CVE-2001-1565

    username/password on command line allows local users to view via "ps" or other process listing programs

  • CVE-2004-1948

    Username/password on command line allows local users to view via "ps" or other process listing programs.

  • CVE-1999-1270

    PGP passphrase provided as command line argument.

  • CVE-2004-1058

    Kernel race condition allows reading of environment variables of a process that is still spawning.

  • CVE-2021-32638

    Code analysis product passes access tokens as a command-line parameter or through an environment variable, making them visible to other processes via the ps command.

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 Java

In the example below, the password for a keystore file is read from a system property.

Vulnerable Java 
String keystorePass = System.getProperty("javax.net.ssl.keyStorePassword");
  if (keystorePass == null) {
  	System.err.println("ERROR: Keystore password not specified.");
  	System.exit(-1);
  }
  ...
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-214

  • 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-214

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

This vulnerability occurs when a process is started with sensitive data, such as passwords or API keys, passed directly in its command-line arguments or environment variables. Because this information is often visible to other processes on the system, it can be easily exposed.

How serious is CWE-214?

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

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

How can I prevent CWE-214?

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

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

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

Related weaknesses

Weaknesses related to CWE-214

CWE-497 Parent

Exposure of Sensitive System Information to an Unauthorized Control Sphere

This vulnerability occurs when an application unintentionally reveals sensitive details about its underlying system, such as file paths,…

CWE-548 Sibling

Exposure of Information Through Directory Listing

This vulnerability occurs when a web server is misconfigured to display a full list of files within a directory instead of serving a…

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.