CWE-214: Invocation of Process Using Visible Sensitive Information

BaseIncomplete

A process is invoked with sensitive command-line arguments, environment variables, or other elements that can be seen by other processes on the operating system.

View on MITRE
Back to CWE Lookup

Extended Description

Many operating systems allow a user to list information about processes that are owned by other users. Other users could see information such as command line arguments or environment variable settings. When this data contains sensitive information such as credentials, it might allow other users to launch an attack against the product or related resources.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-214 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-214, Invocation of Process Using Visible Sensitive Information, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Make elimination of CWE-214 a product outcome

Apply CISA's Secure by Design principle of taking ownership of customer security outcomes to CWE-214, Invocation of Process Using Visible Sensitive Information. Put the weakness in the product threat model and security roadmap, fund class-level design and platform changes, prefer safe defaults and reusable guardrails, and publish measurable progress. Do not transfer the primary burden to customer configuration when the manufacturer can remove or contain the root cause in the product.

Shifting the Balance of Cybersecurity Risk: Secure by Design SoftwareCybersecurity and Infrastructure Security Agency

Connect Invocation of Process Using Visible Sensitive Information to documented attack evidence

Recorded impacts include Read Application Data; observed examples include CVE-2023-38994, CVE-2005-1387, and CVE-2005-2291; related weaknesses include CWE-497. Use these source-defined anchors to turn CWE-214 into implementation, review, and verification checks for the affected component.

CWE-214: Invocation of Process Using Visible Sensitive InformationMITRE CWE

Apply precise root-cause mapping to CWE-214

Apply MITRE's full root-cause mapping guidance when using CWE-214, Invocation of Process Using Visible Sensitive Information. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping GuidanceMITRE CWE

Validate CWE-214 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-214, Invocation of Process Using Visible Sensitive Information. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick TipsMITRE CWE

Frequently Asked Questions

What is CWE-214: Invocation of Process Using Visible Sensitive Information?+

CWE-214: Invocation of Process Using Visible Sensitive Information is a Common Weakness Enumeration (CWE) entry maintained by MITRE. A process is invoked with sensitive command-line arguments, environment variables, or other elements that can be seen by other processes on the operating system. Many operating systems allow a user to list information about processes that are owned by other users. Other users could see information such as command line arguments or environment variable settings. When this data contains sensitive information such as credentials, it might allow other users to launch an attack against the product or related resources.

What are the security consequences of Invocation of Process Using Visible Sensitive Information?+

If exploited, CWE-214 (Invocation of Process Using Visible Sensitive Information) it can compromise Confidentiality, leading to outcomes such as Read Application Data.

Which programming languages are affected by Invocation of Process Using Visible Sensitive Information?+

CWE-214 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Invocation of Process Using Visible Sensitive Information?+

MITRE documents real CVEs mapped to CWE-214, including CVE-2023-38994, CVE-2005-1387, CVE-2005-2291, CVE-2001-1565 and CVE-2004-1948. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-214 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Advertisement