CWE-611 Improper Restriction of XML External Entity Reference

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

• Confidentiality: Read Application Data, 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. By submitting an XML file that defines an external entity with a file:// URI, an attacker can cause the processing application to read the contents of a local file. For example, a URI such as "file:///c:/winnt/win.ini" designates (in Windows) the file C:\Winnt\win.ini, or file:///etc/passwd designates the password file in Unix-based systems. Once the content of the URI is read, it is fed back into the application that is processing the XML. This application may echo back the data (e.g., in an error message), thereby exposing the file contents. • Integrity: Bypass Protection Mechanism — An attacker may supply a crafted DTD using URIs with schemes such as http://, forcing the application to make outgoing HTTP requests to servers that the attacker cannot reach directly, which can be used to bypass firewall restrictions; hide the source of attacks such as port scanning; or otherwise leverage the server's trust relationship with other entities. • Availability: DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory) — The product could consume excessive CPU cycles or memory using a URI that points to a large file, or a device that always returns data such as /dev/random. Alternately, the URI could reference a file that contains many nested or recursive entity references to further slow down parsing.

• [Implementation, System Configuration] Many XML parsers and validators can be configured to disable external entity expansion.

• Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

• CVE-2022-42745: Recruiter software allows reading arbitrary files using XXE • CVE-2005-1306: A browser control can allow remote attackers to determine the existence of files via Javascript containing XML script. • CVE-2012-5656: XXE during SVG image conversion • CVE-2012-2239: XXE in PHP application allows reading the application's configuration file. • CVE-2012-3489: XXE in database server • CVE-2012-4399: XXE in rapid web application development framework allows reading arbitrary files. • CVE-2012-3363: XXE via XML-RPC request. • CVE-2012-0037: XXE in office document product using RDF. • CVE-2011-4107: XXE in web-based administration tool for database. • CVE-2010-3322: XXE in product that performs large-scale data analysis. • CVE-2009-1699: XXE in XSL stylesheet functionality in a common library used by some web browsers.