CWE-827: Improper Control of Document Type Definition

VariantIncomplete

The product does not restrict a reference to a Document Type Definition (DTD) to the intended control sphere. This might allow attackers to reference arbitrary DTDs, possibly causing the product to expose files, consume excessive system resources, or execute arbitrary http requests on behalf of the attacker.

View on MITRE
Back to CWE Lookup

Extended Description

As DTDs are processed, they might try to read or include files on the machine performing the parsing. If an attacker is able to control the DTD, then the attacker might be able to specify sensitive resources or requests or provide malicious content. For example, the SOAP specification prohibits SOAP messages from containing DTDs.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
XML
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-827 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-827, Improper Control of Document Type Definition, 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-827 a product outcome

Apply CISA's Secure by Design principle of taking ownership of customer security outcomes to CWE-827, Improper Control of Document Type Definition. 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 Improper Control of Document Type Definition to documented attack evidence

Recorded impacts include Read Files or Directories, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), Execute Unauthorized Code or Commands, and Gain Privileges or Assume Identity; observed examples include CVE-2010-2076; related weaknesses include CWE-706, CWE-829, and CWE-776. Use these source-defined anchors to turn CWE-827 into implementation, review, and verification checks for the affected component.

CWE-827: Improper Control of Document Type DefinitionMITRE CWE

Apply precise root-cause mapping to CWE-827

Apply MITRE's full root-cause mapping guidance when using CWE-827, Improper Control of Document Type Definition. 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-827 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-827, Improper Control of Document Type Definition. 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-827: Improper Control of Document Type Definition?+

CWE-827: Improper Control of Document Type Definition is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not restrict a reference to a Document Type Definition (DTD) to the intended control sphere. This might allow attackers to reference arbitrary DTDs, possibly causing the product to expose files, consume excessive system resources, or execute arbitrary http requests on behalf of the attacker. As DTDs are processed, they might try to read or include files on the machine performing the parsing. If an attacker is able to control the DTD, then the attacker might be able to specify sensitive resources or requests or provide malicious content. For example, the SOAP specification prohibits SOAP messages from containing DTDs.

What are the security consequences of Improper Control of Document Type Definition?+

If exploited, CWE-827 (Improper Control of Document Type Definition) it can compromise Confidentiality, Availability, Integrity and Access Control, leading to outcomes such as Read Files or Directories, DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), Execute Unauthorized Code or Commands and Gain Privileges or Assume Identity.

Which programming languages are affected by Improper Control of Document Type Definition?+

CWE-827 commonly affects XML. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Improper Control of Document Type Definition?+

MITRE documents real CVEs mapped to CWE-827, including CVE-2010-2076. 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-827 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