The software 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 software 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. 1000 Weakness ChildOf 706 699 Category ChildOf 442 1000 Weakness ChildOf 829 1000 Weakness CanPrecede 776 Confidentiality 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 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). Integrity Confidentiality Availability Access_Control Execute unauthorized code or commands Gain privileges / 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. 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. Daniel Kulp Apache CXF Security Advisory (CVE-2010-2076) 2010-06-16 http://svn.apache.org/repos/asf/cxf/trunk/security/CVE-2010-2076.pdf MITRE 2010-10-25 CWE Content Team MITRE 2011-03-29 updated Relationships CWE Content Team MITRE 2011-06-01 updated Common_Consequences