CWE-829: Inclusion of Functionality from Untrusted Control Sphere

BaseIncomplete

The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.

View on MITRE
Back to CWE Lookup

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-829 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-829, Inclusion of Functionality from Untrusted Control Sphere, 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

Apply Libraries or Frameworks controls for Inclusion of Functionality from Untrusted Control Sphere

MITRE associates mitigation with Architecture and Design, Operation, and Implementation; the listed strategies include Libraries or Frameworks, Enforcement by Conversion, Sandbox or Jail, and Environment Hardening; documented detection approaches include Automated Static Analysis - Binary or Bytecode, Manual Static Analysis - Binary or Bytecode, Dynamic Analysis with Manual Results Interpretation, and Manual Static Analysis - Source Code. Use these source-defined anchors to turn CWE-829 into implementation, review, and verification checks for the affected component.

CWE-829: Inclusion of Functionality from Untrusted Control SphereMITRE CWE

Triage CWE-829 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-829, Inclusion of Functionality from Untrusted Control Sphere, 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 CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-829

Apply MITRE's full root-cause mapping guidance when using CWE-829, Inclusion of Functionality from Untrusted Control Sphere. 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-829 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-829, Inclusion of Functionality from Untrusted Control Sphere. 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-829: Inclusion of Functionality from Untrusted Control Sphere?+

CWE-829: Inclusion of Functionality from Untrusted Control Sphere is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.

What are the security consequences of Inclusion of Functionality from Untrusted Control Sphere?+

If exploited, CWE-829 (Inclusion of Functionality from Untrusted Control Sphere) it can compromise Confidentiality, Integrity and Availability, leading to outcomes such as Execute Unauthorized Code or Commands.

How is Inclusion of Functionality from Untrusted Control Sphere detected?+

CWE-829 can be detected using Automated Static Analysis - Binary or Bytecode, Manual Static Analysis - Binary or Bytecode, Dynamic Analysis with Manual Results Interpretation, Manual Static Analysis - Source Code, Automated Static Analysis - Source Code and Architecture or Design Review. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Inclusion of Functionality from Untrusted Control Sphere?+

CWE-829 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 Inclusion of Functionality from Untrusted Control Sphere?+

MITRE documents real CVEs mapped to CWE-829, including CVE-2010-2076, CVE-2004-0285, CVE-2004-0030, CVE-2004-0068 and CVE-2005-2157. 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-829 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