The GenericConsumer class in the Consumer component in ZendOpenId before 2.0.2 and the Zend_OpenId_Consumer class in Zend Framework 1 before 1.12.4 does not verify that the openid_op_endpoint value identifies the same Identity Provider as the provider used in the association handle, which allows remote attackers to bypass authentication and spoof arbitrary OpenID identities by using a malicious OpenID Provider that generates OpenID tokens with arbitrary identifier and claimed_id values.

Versions of Zend Framework earlier than 1.12.4 are vulnerable to the following security flaws :

 - A flaw exists in the 'Consumer' component, as it is possible to login using an arbitrary OpenID account without knowing any secret information.  With a specially crafted OpenID Provider, a remote attacker can impersonate any OpenID Identity to bypass the authentication mechanism. (CVE-2014-2684)
 - A flaw in the 'Consumer' component, as elements in OpenID tokens are not properly checked to ensure they're signed.  The framework considers a single signed element as sufficient whereas the specification states that more elements are required to be signed if present.  This may allow a remote attacker to cause insufficiently signed OpenID tokens to be accepted as valid. (CVE-2014-2685)

The previous zendframework upload incorrectly fixes CVE-2015-3154, causing a regression. This update corrects this problem. Thanks to &#x415;&#x432;&#x433;&#x435;&#x43D;&#x438;&#x439;
&#x421;&#x43C;&#x43E;&#x43B;&#x438;&#x43D; (Evgeny Smolin) <esmolin@inbox.ru>.

CVE-2012-6531

P&aacute;draic Brady identified a weakness to handle the SimpleXMLElement zendframework class, allowing to remote attackers to read arbitrary files or create TCP connections via an XML external entity (XXE) injection attack.

CVE-2012-6532

P&aacute;draic Brady found that remote attackers could cause a denial of service by CPU consumption, via recursive or circular references through an XML entity expansion (XEE) attack.

CVE-2014-2681

Lukas Reschke reported a lack of protection against XML External Entity injection attacks in some functions. This fix extends the incomplete one from CVE-2012-5657.

CVE-2014-2682

Lukas Reschke reported a failure to consider that the libxml_disable_entity_loader setting is shared among threads in the PHP-FPM case. This fix extends the incomplete one from CVE-2012-5657.

CVE-2014-2683

Lukas Reschke reported a lack of protection against XML Entity Expansion attacks in some functions. This fix extends the incomplete one from CVE-2012-6532.

CVE-2014-2684

Christian Mainka and Vladislav Mladenov from the Ruhr-University Bochum reported an error in the consumer's verify method that lead to acceptance of wrongly sourced tokens.

CVE-2014-2685

Christian Mainka and Vladislav Mladenov from the Ruhr-University Bochum reported a specification violation in which signing of a single parameter is incorrectly considered sufficient.

CVE-2014-4914

Cassiano Dal Pizzol discovered that the implementation of the ORDER BY SQL statement in Zend_Db_Select contains a potential SQL injection when the query string passed contains parentheses.

CVE-2014-8088

Yury Dyachenko at Positive Research Center identified potential XML eXternal Entity injection vectors due to insecure usage of PHP's DOM extension.

CVE-2014-8089

Jonas Sandstr&ouml;m discovered a SQL injection vector when manually quoting value for sqlsrv extension, using null byte.

CVE-2015-3154

Filippo Tessarotto and Maks3w reported potential CRLF injection attacks in mail and HTTP headers.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Multiple vulnerabilities were discovered in Zend Framework, a PHP framework. Except for CVE-2015-3154, all these issues were already fixed in the version initially shipped with Jessie.

  - CVE-2014-2681     Lukas Reschke reported a lack of protection against XML     External Entity injection attacks in some functions.
    This fix extends the incomplete one from CVE-2012-5657.

  - CVE-2014-2682     Lukas Reschke reported a failure to consider that the     libxml_disable_entity_loader setting is shared among     threads in the PHP-FPM case. This fix extends the     incomplete one from CVE-2012-5657.

  - CVE-2014-2683     Lukas Reschke reported a lack of protection against XML     Entity Expansion attacks in some functions. This fix     extends the incomplete one from CVE-2012-6532.

  - CVE-2014-2684     Christian Mainka and Vladislav Mladenov from the     Ruhr-University Bochum reported an error in the     consumer's verify method that lead to acceptance of     wrongly sourced tokens.

  - CVE-2014-2685     Christian Mainka and Vladislav Mladenov from the     Ruhr-University Bochum reported a specification     violation in which signing of a single parameter is     incorrectly considered sufficient.

  - CVE-2014-4914     Cassiano Dal Pizzol discovered that the implementation     of the ORDER BY SQL statement in Zend_Db_Select contains     a potential SQL injection when the query string passed     contains parentheses.

  - CVE-2014-8088     Yury Dyachenko at Positive Research Center identified     potential XML eXternal Entity injection vectors due to     insecure usage of PHP's DOM extension.

  - CVE-2014-8089     Jonas Sandstrom discovered a SQL injection vector when     manually quoting value for sqlsrv extension, using null     byte.

  - CVE-2015-3154     Filippo Tessarotto and Maks3w reported potential CRLF     injection attacks in mail and HTTP headers.

Updated php-ZendFramework packages fix multiple vulnerabilities :

XML eXternal Entity (XXE) and XML Entity Expansion (XEE) flaws were discovered in the Zend Framework. An attacker could use these flaws to cause a denial of service, access files accessible to the server process, or possibly perform other more advanced XML External Entity (XXE) attacks (CVE-2014-2681, CVE-2014-2682, CVE-2014-2683).

Using the Consumer component of Zend_OpenId, it is possible to login using an arbitrary OpenID account (without knowing any secret information) by using a malicious OpenID Provider. That means OpenID it is possible to login using arbitrary OpenID Identity (MyOpenID, Google, etc), which are not under the control of our own OpenID Provider. Thus, we are able to impersonate any OpenID Identity against the framework (CVE-2014-2684, CVE-2014-2685).

The implementation of the ORDER BY SQL statement in Zend_Db_Select of Zend Framework 1 contains a potential SQL injection when the query string passed contains parentheses (CVE-2014-4914).

Due to a bug in PHP's LDAP extension, when ZendFramework's Zend_ldap class is used for logins, an attacker can login as any user by using a null byte to bypass the empty password check and perform an unauthenticated LDAP bind (CVE-2014-8088).

The sqlsrv PHP extension, which provides the ability to connect to Microsoft SQL Server from PHP, does not provide a built-in quoting mechanism for manually quoting values to pass via SQL queries;
developers are encouraged to use prepared statements. Zend Framework provides quoting mechanisms via Zend_Db_Adapter_Sqlsrv which uses the recommended double single quote ('') as quoting delimiters. SQL Server treats null bytes in a query as a string terminator, allowing an attacker to add arbitrary SQL following a null byte, and thus create a SQL injection (CVE-2014-8089).

The GenericConsumer class in the Consumer component in ZendOpenId before 2.0.2 and the Zend_OpenId_Consumer class in Zend Framework 1 before 1.12.4 violate the OpenID 2.0 protocol by ensuring only that at least one field is signed, which allows remote attackers to bypass authentication by leveraging an assertion from an OpenID provider.

XML eXternal Entity (XXE) and XML Entity Expansion (XEE) flaws were discovered in the Zend Framework. An attacker could use these flaws to cause a denial of service, access files accessible to the server process, or possibly perform other more advanced XML External Entity (XXE) attacks.

Using the Consumer component of ZendOpenId (or Zend_OpenId in ZF1), it is possible to login using an arbitrary OpenID account (without knowing any secret information) by using a malicious OpenID Provider.
That means OpenID it is possible to login using arbitrary OpenID Identity (MyOpenID, Google, etc), which are not under the control of our own OpenID Provider. Thus, we are able to impersonate any OpenID Identity against the framework.

Moreover, the Consumer accepts OpenID tokens with arbitrary signed elements. The framework does not check if, for example, both openid.claimed_id and openid.endpoint_url are signed. It is just sufficient to sign one parameter. According to https://openid.net/specs/openid-authentication-2_0.html#positive_asser tions, at least op_endpoint, return_to, response_nonce, assoc_handle, and, if present in the response, claimed_id and identity, must be signed.

update to 1.12.5 fixes http://framework.zend.com/security/advisory/ZF2014-01 fixes http://framework.zend.com/security/advisory/ZF2014-02 removed:
InfoCards, Services/Nirvanix

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Upstream release notes:
https://github.com/zendframework/zf2/releases/tag/release-2.2.6

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Updated php-ZendFramework packages fix security vulnerabilities :

XML eXternal Entity (XXE) and XML Entity Expansion (XEE) flaws were discovered in the Zend Framework. An attacker could use these flaws to cause a denial of service, access files accessible to the server process, or possibly perform other more advanced XML External Entity (XXE) attacks (CVE-2014-2681, CVE-2014-2682, CVE-2014-2683).

Using the Consumer component of Zend_OpenId, it is possible to login using an arbitrary OpenID account (without knowing any secret information) by using a malicious OpenID Provider. That means OpenID it is possible to login using arbitrary OpenID Identity (MyOpenID, Google, etc), which are not under the control of our own OpenID Provider. Thus, we are able to impersonate any OpenID Identity against the framework (CVE-2014-2684, CVE-2014-2685).

ID	Name	Product	Family	Severity
9150	Zend Framework < 1.12.4 Multiple Vulnerabilities	Nessus Network Monitor	CGI	critical
84297	Debian DLA-251-2 : zendframework regression update	Nessus	Debian Local Security Checks	critical
83748	Debian DSA-3265-1 : zendframework - security update	Nessus	Debian Local Security Checks	critical
82350	Mandriva Linux Security Advisory : php-ZendFramework (MDVSA-2015:097)	Nessus	Mandriva Local Security Checks	high
78320	Amazon Linux AMI : php-ZendFramework (ALAS-2014-377)	Nessus	Amazon Linux Local Security Checks	high
73506	Fedora 20 : php-ZendFramework-1.12.5-1.fc20 (2014-4651)	Nessus	Fedora Local Security Checks	high
73505	Fedora 19 : php-ZendFramework2-2.2.6-1.fc19 (2014-4636)	Nessus	Fedora Local Security Checks	high
73503	Fedora 20 : php-ZendFramework2-2.2.6-1.fc20 (2014-4612)	Nessus	Fedora Local Security Checks	high
73502	Fedora 19 : php-ZendFramework-1.12.5-1.fc19 (2014-4603)	Nessus	Fedora Local Security Checks	high
73447	Mandriva Linux Security Advisory : php-ZendFramework (MDVSA-2014:072)	Nessus	Mandriva Local Security Checks	high

Detections

Analytics

CVE-2014-2684

critical

Tenable Plugins

critical

critical

critical

high

high

high

high

high

high

high