CWE-69: Improper Handling of Windows ::DATA Alternate Data Stream

Extended Description

An attacker can use an ADS to hide information about a file (e.g. size, the name of the process) from a system or file browser tools such as Windows Explorer and 'dir' at the command line utility. Alternately, the attacker might be able to bypass intended access restrictions for the associated data fork.

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-69 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-69, Improper Handling of Windows ::DATA Alternate Data Stream, 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 Framework — National Institute of Standards and Technology

Address Improper Handling of Windows ::DATA Alternate Data Stream during Implementation

MITRE associates mitigation with Implementation; documented detection approaches include Automated Analysis; recorded impacts include Bypass Protection Mechanism, Hide Activities, and Other. Use these source-defined anchors to turn CWE-69 into implementation, review, and verification checks for the affected component.

CWE-69: Improper Handling of Windows ::DATA Alternate Data Stream — MITRE CWE

Triage CWE-69 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-69, Improper Handling of Windows ::DATA Alternate Data Stream, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-69

Apply MITRE's full root-cause mapping guidance when using CWE-69, Improper Handling of Windows ::DATA Alternate Data Stream. 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 Guidance — MITRE CWE

Validate CWE-69 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-69, Improper Handling of Windows ::DATA Alternate Data Stream. 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 Tips — MITRE CWE

Frequently Asked Questions

What is CWE-69: Improper Handling of Windows ::DATA Alternate Data Stream?+

CWE-69: Improper Handling of Windows ::DATA Alternate Data Stream is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not properly prevent access to, or detect usage of, alternate data streams (ADS). An attacker can use an ADS to hide information about a file (e.g. size, the name of the process) from a system or file browser tools such as Windows Explorer and 'dir' at the command line utility. Alternately, the attacker might be able to bypass intended access restrictions for the associated data fork.

What are the security consequences of Improper Handling of Windows ::DATA Alternate Data Stream?+

If exploited, CWE-69 (Improper Handling of Windows ::DATA Alternate Data Stream) it can compromise Access Control, Non-Repudiation and Other, leading to outcomes such as Bypass Protection Mechanism, Hide Activities and Other.

How do you prevent or mitigate Improper Handling of Windows ::DATA Alternate Data Stream?+

Recommended mitigations for CWE-69 include: Ensure that the source code correctly parses the filename to read or write to the correct stream.

How is Improper Handling of Windows ::DATA Alternate Data Stream detected?+

CWE-69 can be detected using Automated Analysis. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Improper Handling of Windows ::DATA Alternate Data Stream?+

CWE-69 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 Improper Handling of Windows ::DATA Alternate Data Stream?+

MITRE documents real CVEs mapped to CWE-69, including CVE-1999-0278 and CVE-2000-0927. 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-69 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.

CWE-69: Improper Handling of Windows ::DATA Alternate Data Stream

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods

Method

Description

Code Examples & CVEs

Observed CVE Examples (2)

CWE Relationships

Parent Weaknesses