CVE-2012-3363 : Detail

CVE-2012-3363

9.1
/
CRITICAL
A05-Security Misconfiguration
26.4%V3
Network
2013-02-13 16:00 +00:00
2013-12-02 12:57 +00:00

Alert for a CVE

Stay informed of any changes for a specific CVE.
Alert management

Descriptions

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.

Informations

Related Weaknesses

CWE-ID Weakness Name Source
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.

Metrics

Metric Score Severity CVSS Vector Source
V3.1 9.1 CRITICAL CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

nvd@nist.gov
V2 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N nvd@nist.gov

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

Exploit information

Exploit Database EDB-ID : 19408

Publication date : 2012-06-26 22:00 +00:00
Author : SEC Consult
EDB Verified : No

SEC Consult Vulnerability Lab Security Advisory < 20120626-0 > ======================================================================= title: Local file disclosure via XXE injection product: Zend Framework vulnerable version: 1.11.11 1.12.0 RC1 2.0.0 beta4 and earlier versions / branches fixed version: 1.11.12 1.12.0 RC2 2.0.0 beta5 / trunk impact: Critical homepage: http://framework.zend.com/ found: 2012-06-18 by: K. Gudinavicius SEC Consult Vulnerability Lab https://www.sec-consult.com ======================================================================= Vendor description: ------------------- "Extending the art & spirit of PHP, Zend Framework is based on simplicity, object-oriented best practices, corporate friendly licensing, and a rigorously tested agile codebase. Zend Framework is focused on building more secure, reliable, and modern Web 2.0 applications & web services, and consuming widely available APIs from leading vendors like Google, Amazon, Yahoo!, Flickr, as well as API providers and cataloguers like StrikeIron and ProgrammableWeb." Source: http://framework.zend.com/about/overview Vulnerability overview/description: ----------------------------------- The XmlRpc package of Zend Framework is vulnerable to XML eXternal Entity Injection attacks (both server and client). The SimpleXMLElement class (SimpleXML PHP extension) is used in an insecure way to parse XML data. External entities can be specified by adding a specific DOCTYPE element to XML-RPC requests. By exploiting this vulnerability an application may be coerced to open arbitrary files and/or TCP connections. Other software that uses the XmlRpc package of Zend Framework is then also vulnerable to XML eXternal Entity Injection attacks! Proof of concept: ----------------- For example, the loadXml function (Zend\XmlRpc\Request.php and Response.php) fails to disable external entities when parsing XML data. There is no call to the libxml_disable_entity_loader function before initializing the SimpleXMLElement class. Related code excerpt: public function loadXml($request) { if (!is_string($request)) { $this->_fault = new Zend_XmlRpc_Fault(635); $this->_fault->setEncoding($this->getEncoding()); return false; } try { $xml = new SimpleXMLElement($request); } catch (Exception $e) { // Not valid XML $this->_fault = new Zend_XmlRpc_Fault(631); $this->_fault->setEncoding($this->getEncoding()); return false; } [...] } If a web application uses the Zend_XmlRpc_Server() class (Zend\XmlRpc\Server.php) to handle XML-RPC requests, it is possible to disclose arbitrary local files from the remote system. The following HTTP POST request to the vulnerable XmlRpc server application illustrates the exploitation of this vulnerability. POST /xmlrpc_server.php HTTP/1.1 Host: $host ]> &xxe; Vulnerable / tested versions: ----------------------------- The vulnerability has been verified to exist in versions 1.11.11 and 2.0.0beta4 of Zend Framework, which were the most recent versions at the time of discovery. Furthermore, previous versions and 1.12.0 RC1 are also affected. Older branches are also affected but won't be fixed by Zend as they are not maintained anymore. Their policy is to fix the current minor release and the immediate previous minor release. Vendor contact timeline: ------------------------ 2012-06-18: Contacting vendor through zf-security@zend.com 2012-06-18: Vendor: Very fast reply, fixes issue already after 3 hours! 2012-06-18: Confirming server-side fix, adding recommendation for XmlRpc client code 2012-06-19: Vendor: XmlRpc client code also fixed Confirming fix 2012-06-20: Contacting local CERT 2012-06-20: Vendor: starts packaging, expected release of 1.11.12 and 1.12.0RC2 by end of week, ZF2 trunk already fixed, next beta 2.0.0beta5 will be released late next week 2012-06-22: Vendor: Packages are created and staged, packages and security announcement will be released on Monday 2012-06-25: New packages and Zend security advisory released by vendor 2012-06-26: SEC Consult releases security advisory Solution: --------- Upgrade to the latest version available, e.g. * v1.11.12 * v1.12.0 RC2 * update ZF2 master trunk If you are using an older branch you are urged to upgrade! Zend framework security advisory: http://framework.zend.com/security/advisory/ZF2012-01 Download link for new releases: http://framework.zend.com/download/latest Commits: -------- http://framework.zend.com/code/log.php?repname=Zend+Framework&path=%2F * Zend Framework 1.X Trunk: http://framework.zend.com/code/revision.php?repname=Zend+Framework&path=%2Ftrunk&rev=24970&peg=24970 http://framework.zend.com/code/revision.php?repname=Zend+Framework&path=%2F&rev=24975 * 1.11.X: http://framework.zend.com/code/revision.php?repname=Zend+Framework&path=%2Fbranches%2F&rev=24971&peg=24971 http://framework.zend.com/code/revision.php?repname=Zend+Framework&path=%2Fbranches%2F&rev=24972&peg=24972 http://framework.zend.com/code/revision.php?repname=Zend+Framework&path=%2F&rev=24976 * 1.12.0: http://framework.zend.com/code/revision.php?repname=Zend+Framework&path=%2Fbranches%2F&rev=24973&peg=24973 http://framework.zend.com/code/revision.php?repname=Zend+Framework&path=%2F&rev=24977 * Zend Framework 2.0 https://github.com/zendframework/zf2/pull/1523 Workaround: ----------- None Advisory URL: ------------- https://www.sec-consult.com/en/advisories.html ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SEC Consult Unternehmensberatung GmbH Office Vienna Mooslackengasse 17 A-1190 Vienna Austria Tel.: +43 / 1 / 890 30 43 - 0 Fax.: +43 / 1 / 890 30 43 - 25 Mail: research at sec-consult dot com https://www.sec-consult.com EOF K. Gudinavicius, J. Greil / @2012

Products Mentioned

Configuraton 0

Zend>>Zend_framework >> Version From (including) 1.0.0 To (excluding) 1.11.12

Zend>>Zend_framework >> Version 1.12.0

Zend>>Zend_framework >> Version 1.12.0

Zend>>Zend_framework >> Version 1.12.0

Zend>>Zend_framework >> Version 1.12.0

Configuraton 0

Fedoraproject>>Fedora >> Version 17

Fedoraproject>>Fedora >> Version 18

Configuraton 0

Debian>>Debian_linux >> Version 6.0

References

http://www.openwall.com/lists/oss-security/2012/06/27/2
Tags : mailing-list, x_refsource_MLIST
http://www.debian.org/security/2012/dsa-2505
Tags : vendor-advisory, x_refsource_DEBIAN
http://www.openwall.com/lists/oss-security/2012/06/26/4
Tags : mailing-list, x_refsource_MLIST
http://www.openwall.com/lists/oss-security/2012/06/26/2
Tags : mailing-list, x_refsource_MLIST
http://openwall.com/lists/oss-security/2013/03/25/2
Tags : mailing-list, x_refsource_MLIST
http://www.securitytracker.com/id?1027208
Tags : vdb-entry, x_refsource_SECTRACK
Click on the button to the left (OFF), to authorize the inscription of cookie improving the functionalities of the site. Click on the button to the left (Accept all), to unauthorize the inscription of cookie improving the functionalities of the site.