In Dell EMC Unisphere for VMAX Virtual Appliance versions prior to 8.4.0.8, Dell EMC Solutions Enabler Virtual Appliance versions prior to 8.4.0.8, Dell EMC VASA Provider Virtual Appliance versions prior to 8.4.0.512, Dell EMC SMIS versions prior to 8.4.0.6, Dell EMC VMAX Embedded Management (eManagement) versions prior to and including 1.4.0.347, Dell EMC VNX2 Operating Environment (OE) for File versions prior to 8.1.9.231, Dell EMC VNX2 Operating Environment (OE) for Block versions prior to 05.33.009.5.231, Dell EMC VNX1 Operating Environment (OE) for File versions prior to 7.1.82.0, Dell EMC VNX1 Operating Environment (OE) for Block versions prior to 05.32.000.5.225, Dell EMC VNXe3200 Operating Environment (OE) all versions, Dell EMC VNXe1600 Operating Environment (OE) versions prior to 3.1.9.9570228, Dell EMC VNXe 3100/3150/3300 Operating Environment (OE) all versions, Dell EMC ViPR SRM versions 3.7, 3.7.1, 3.7.2 (only if using Dell EMC Host Interface for Windows), Dell EMC ViPR SRM versions 4.0, 4.0.1, 4.0.2, 4.0.3 (only if using Dell EMC Host Interface for Windows), Dell EMC XtremIO versions 4.x, Dell EMC VMAX eNAS version 8.x, Dell EMC Unity Operating Environment (OE) versions prior to 4.3.0.1522077968, ECOM is affected by a XXE injection vulnerability due to the configuration of the XML parser shipped with the product. XXE Injection attack may occur when XML input containing a reference to an external entity (defined by the attacker) is processed by an affected XML parser. XXE Injection may allow attackers to gain unauthorized access to files containing sensitive information or may be used to cause denial-of-service.
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.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Emc_smis | Dell | * | 8.4.0.6 (excluding) |
| Emc_solutions_enabler_virtual_appliance | Dell | * | 8.4.0.8 (excluding) |
| Emc_unisphere | Dell | * | 8.4.0.8 (excluding) |
| Emc_unity_operating_environment | Dell | * | 4.3.0.1522077968 (excluding) |
| Emc_vasa_provider_virtual_appliance | Dell | * | 8.4.0.512 (excluding) |
| Emc_vipr_srm | Dell | - (including) | - (including) |
| Emc_vipr_srm | Dell | 3.7 (including) | 3.7 (including) |
| Emc_vipr_srm | Dell | 3.7.1 (including) | 3.7.1 (including) |
| Emc_vipr_srm | Dell | 3.7.2 (including) | 3.7.2 (including) |
| Emc_vipr_srm | Dell | 4.0 (including) | 4.0 (including) |
| Emc_vipr_srm | Dell | 4.0.1 (including) | 4.0.1 (including) |
| Emc_vipr_srm | Dell | 4.0.2 (including) | 4.0.2 (including) |
| Emc_vipr_srm | Dell | 4.0.3 (including) | 4.0.3 (including) |
| Emc_vmax_embedded_management | Dell | * | 1.4.0.347 (including) |
| Emc_vmax_enas | Dell | 8.0 (including) | 8.0 (including) |
| Emc_vmax_enas | Dell | 8.0.1 (including) | 8.0.1 (including) |
| Emc_vnx1_operating_environment | Dell | 05.32.000.5.225 (including) | 05.32.000.5.225 (including) |
| Emc_vnx1_operating_environment | Dell | 7.1.82.0 (including) | 7.1.82.0 (including) |
| Emc_vnx2_operating_environment | Dell | * | 05.33.009.5.231 (excluding) |
| Emc_vnx2_operating_environment | Dell | * | 8.1.9.231 (excluding) |
| Emc_vnxe_3100_operating_environment | Dell | - (including) | - (including) |
| Emc_vnxe_3150_operating_environment | Dell | - (including) | - (including) |
| Emc_vnxe_3300__operating_environment | Dell | - (including) | - (including) |
| Emc_vnxe1600_operating_environment | Dell | * | 3.1.9.9570228 (excluding) |
| Emc_vnxe3200_operating_environment | Dell | - (including) | - (including) |
| Emc_xtremio | Dell | 4.0 (including) | 4.0 (including) |
| Emc_xtremio | Dell | 4.0.2 (including) | 4.0.2 (including) |
XML documents optionally contain a Document Type Definition (DTD), which, among other features, enables the definition of XML entities. It is possible to define an entity by providing a substitution string in the form of a URI. The XML parser can access the contents of this URI and embed these contents back into the XML document for further processing. 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. Using URIs with other schemes such as http://, the attacker can force the application to make outgoing requests to servers that the attacker cannot reach directly, which can be used to bypass firewall restrictions or hide the source of attacks such as port scanning. 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.