A security flaw was found in the way Plone, a user friendly and powerful content management system, performed permission checks on certain objects with incomplete security declarations. A remote attacker, with the privilege to author RestrictedPython code, could use this flaw to gain a partial escape from the sandbox mechanism, leading to their ability (in a retricted way) to use full Python routines. References: [1] http://plone.org/products/plone/security/advisories/20121106/05 [2] http://plone.org/products/plone/security/advisories/20121106/ Relevant upstream HotFixes: [3] http://plone.org/products/plone-hotfix/releases/20121106 From the OSS post: [4] http://www.openwall.com/lists/oss-security/2012/11/07/4 the get_request_var_or_attr.py change from upstream HotFix is relevant to this issue.
Reference: https://bugs.launchpad.net/zope2/+bug/1079238
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.