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.
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| CanPrecede | Allowed | B | 776 | Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion') |
| ChildOf | Allowed-with-Review | C | 706 | Use of Incorrectly-Resolved Name or Reference |
| ChildOf | Allowed | B | 829 | Inclusion of Functionality from Untrusted Control Sphere |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1011 | Authorize Actors |
| MemberOf | Prohibited | C | 1416 | Comprehensive Categorization: Resource Lifecycle Management |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | BS | BOSS-245 | Weaknesses in Software Written in XML |
| MemberOf | Prohibited | BS | BOSS-311 | Execute Unauthorized Code or Commands (impact) |
| MemberOf | Prohibited | BS | BOSS-314 | DoS: Resource Consumption (CPU) (impact) |
| MemberOf | Prohibited | BS | BOSS-319 | Read Files or Directories (impact) |
| MemberOf | Prohibited | BS | BOSS-327 | DoS: Resource Consumption (Memory) (impact) |
| MemberOf | Prohibited | BS | BOSS-332 | Gain Privileges or Assume Identity (impact) |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 1011 | Authorize Actors |
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| Confidentiality | N/A | Read Files or Directories | If the attacker is able to include a crafted DTD and a default entity resolver is enabled, the attacker may be able to access arbitrary files on the system. |
| Availability | N/A | DoS: Resource Consumption (CPU)DoS: Resource Consumption (Memory) | The DTD may cause the parser to consume excessive CPU cycles or memory using techniques such as nested or recursive entity references (CWE-776). |
| IntegrityConfidentialityAvailabilityAccess Control | N/A | Execute Unauthorized Code or CommandsGain Privileges or Assume Identity | The DTD may include arbitrary HTTP requests that the server may execute. This could lead to other attacks leveraging the server's trust relationship with other entities. |
If the attacker is able to include a crafted DTD and a default entity resolver is enabled, the attacker may be able to access arbitrary files on the system.
The DTD may cause the parser to consume excessive CPU cycles or memory using techniques such as nested or recursive entity references (CWE-776).
The DTD may include arbitrary HTTP requests that the server may execute. This could lead to other attacks leveraging the server's trust relationship with other entities.
REALIZATION: This weakness is caused during implementation of an architectural security tactic.
| Reference | Description |
|---|---|
| CVE-2010-2076 | Product does not properly reject DTDs in SOAP messages, which allows remote attackers to read arbitrary files, send HTTP requests to intranet servers, or cause a denial of service. |
| Ordinality | Description |
|---|
This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|
| ID | Name |
|---|