A HTTP header injection flaw was found in the way Plone, a user friendly and powerful content management system, performed sanitization of HTTP headers provided within certain URL requests. A remote attacker could provide a specially-crafted URL that, when processed would lead the injected HTTP headers to be returned as part of Plone system HTTP response (possibly leading to HTTP response splitting, cross-site scripting [XSS] flaws, session fixation or unauthorized HTTP redirect attacks - to mention some of the possible negative consequences). References: [1] http://plone.org/products/plone/security/advisories/20121106/02 [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 setHeader.py change from upstream HotFix is relevant to this issue.
Reference: https://bugs.launchpad.net/zope2/+bug/930812
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 affect plone as provided with the conga package on Red Hat Enterprise Linux 5.
IssueDescription: It was discovered that Plone, included as a part of luci, did not properly sanitize HTTP headers provided within certain URL requests. A remote attacker could use a specially crafted URL that, when processed, would cause the injected HTTP headers to be returned as a part of the Plone HTTP response, potentially allowing the attacker to perform other more advanced attacks.
This issue has been addressed in the following products: Red Hat Enterprise Linux 5 Via RHSA-2014:1194 https://rhn.redhat.com/errata/RHSA-2014-1194.html