CVE Vulnerabilities

CVE-2012-3363

Improper Restriction of XML External Entity Reference

Published: Feb 13, 2013 | Modified: Feb 15, 2024
CVSS 3.x
9.1
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS 2.x
6.4 MEDIUM
AV:N/AC:L/Au:N/C:P/I:P/A:N
RedHat/V2
RedHat/V3
Ubuntu
MEDIUM

Zend_XmlRpc in Zend Framework 1.x before 1.11.12 and 1.12.x before 1.12.0 does not properly handle SimpleXMLElement classes, which allows remote attackers to read arbitrary files or create TCP connections via an external entity reference in a DOCTYPE element in an XML-RPC request, aka an XML external entity (XXE) injection attack.

Weakness

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.

Affected Software

Name Vendor Start Version End Version
Zend_framework Zend 1.0.0 (including) 1.11.12 (excluding)
Zend_framework Zend 1.12.0-rc1 (including) 1.12.0-rc1 (including)
Zend_framework Zend 1.12.0-rc2 (including) 1.12.0-rc2 (including)
Zend_framework Zend 1.12.0-rc3 (including) 1.12.0-rc3 (including)
Zend_framework Zend 1.12.0-rc4 (including) 1.12.0-rc4 (including)
Zend-framework Ubuntu esm-apps/xenial *
Zend-framework Ubuntu hardy *
Zend-framework Ubuntu lucid *
Zend-framework Ubuntu natty *
Zend-framework Ubuntu oneiric *
Zend-framework Ubuntu precise *
Zend-framework Ubuntu quantal *
Zend-framework Ubuntu raring *
Zend-framework Ubuntu saucy *
Zend-framework Ubuntu trusty *
Zend-framework Ubuntu upstream *
Zend-framework Ubuntu utopic *
Zend-framework Ubuntu vivid *
Zend-framework Ubuntu wily *
Zend-framework Ubuntu xenial *
Zend-framework Ubuntu yakkety *
Zendframework Ubuntu lucid *
Zendframework Ubuntu upstream *

Extended Description

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.

Potential Mitigations

References