It was reported that the authentication system of Plone, a user friendly and powerful content management system based on Zope, was absenting a equality test, that would run in constant time complexity, when validating tickets and verifying identifiers for their equality. A remote attacker with fast network connection to the server could use this flaw to check hash prefixes. References: [1] http://plone.org/products/plone/security/advisories/20121106/23 [2] http://plone.org/products/plone/security/advisories/20121106/ Relevant upstream HotFixes: [3] http://plone.org/products/plone-hotfix/releases/20121106 (utils.py, crypto_oracle.py, and crypto_oracle_p3.py changes seem to be relevant for this issue)
From OSS post: [4] http://www.openwall.com/lists/oss-security/2012/11/07/4 relevant upstream HotFix change related to this issue is django_crypto.py.
The CVE identifier of CVE-2012-5507 has been assigned to this issue: http://www.openwall.com/lists/oss-security/2012/11/10/1
Reference: https://bugs.launchpad.net/zope2/+bug/1071067
This issue may affect the version of plone as shipped with EPEL5, however the latest version there is 3.1.6 (and the latest 3.x release is 3.3.5, which was released a year prior to this flaw being discovered). Given the age of the EPEL5 package and its lack of support, we do not recommend anyone use it. This issue does not affect plone as provided with the conga package on Red Hat Enterprise Linux 5. Statement: Not vulnerable. This issue did not affect the versions of luci (as provided by conga) as shipped with Red Hat Enterprise Linux 5.