First published: Thu Nov 08 2012(Updated: )
A security flaw was found in the way Plone, a user friendly and powerful content management system, performed permissions checks for change titles of content items action. A remote attacker (anonymous user) could submit a specially-crafted HTTP POST request that, when processed, would allow them in an unauthorized way to change titles of content items. References: [1] <a href="http://plone.org/products/plone/security/advisories/20121106/16">http://plone.org/products/plone/security/advisories/20121106/16</a> [2] <a href="http://plone.org/products/plone/security/advisories/20121106/">http://plone.org/products/plone/security/advisories/20121106/</a> Relevant upstream HotFixes: [3] <a href="http://plone.org/products/plone-hotfix/releases/20121106">http://plone.org/products/plone-hotfix/releases/20121106</a> From the OSS post: [4] <a href="http://www.openwall.com/lists/oss-security/2012/11/07/4">http://www.openwall.com/lists/oss-security/2012/11/07/4</a> the renameObjectsByPaths.py change from upstream HotFix is relevant to this issue.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Plone Plone | <=4.2.2 | |
Plone Plone | =1.0 | |
Plone Plone | =1.0.1 | |
Plone Plone | =1.0.2 | |
Plone Plone | =1.0.3 | |
Plone Plone | =1.0.4 | |
Plone Plone | =1.0.5 | |
Plone Plone | =1.0.6 | |
Plone Plone | =2.0 | |
Plone Plone | =2.0.1 | |
Plone Plone | =2.0.2 | |
Plone Plone | =2.0.3 | |
Plone Plone | =2.0.4 | |
Plone Plone | =2.0.5 | |
Plone Plone | =2.1 | |
Plone Plone | =2.1.1 | |
Plone Plone | =2.1.2 | |
Plone Plone | =2.1.3 | |
Plone Plone | =2.1.4 | |
Plone Plone | =2.5 | |
Plone Plone | =2.5.1 | |
Plone Plone | =2.5.2 | |
Plone Plone | =2.5.3 | |
Plone Plone | =2.5.4 | |
Plone Plone | =2.5.5 | |
Plone Plone | =3.0 | |
Plone Plone | =3.0.1 | |
Plone Plone | =3.0.2 | |
Plone Plone | =3.0.3 | |
Plone Plone | =3.0.4 | |
Plone Plone | =3.0.5 | |
Plone Plone | =3.0.6 | |
Plone Plone | =3.1 | |
Plone Plone | =3.1.1 | |
Plone Plone | =3.1.2 | |
Plone Plone | =3.1.3 | |
Plone Plone | =3.1.4 | |
Plone Plone | =3.1.5.1 | |
Plone Plone | =3.1.6 | |
Plone Plone | =3.1.7 | |
Plone Plone | =3.2 | |
Plone Plone | =3.2.1 | |
Plone Plone | =3.2.2 | |
Plone Plone | =3.2.3 | |
Plone Plone | =3.3 | |
Plone Plone | =3.3.1 | |
Plone Plone | =3.3.2 | |
Plone Plone | =3.3.3 | |
Plone Plone | =3.3.4 | |
Plone Plone | =3.3.5 | |
Plone Plone | =4.0 | |
Plone Plone | =4.0.1 | |
Plone Plone | =4.0.2 | |
Plone Plone | =4.0.3 | |
Plone Plone | =4.0.4 | |
Plone Plone | =4.0.5 | |
Plone Plone | =4.0.6.1 | |
Plone Plone | =4.1 | |
Plone Plone | =4.1.4 | |
Plone Plone | =4.1.5 | |
Plone Plone | =4.1.6 | |
Plone Plone | =4.2 | |
Plone Plone | =4.2.1 | |
Plone Plone | =4.3 | |
pip/plone | >=4.3a1<4.3b1 | 4.3b1 |
pip/plone | <4.2.3 | 4.2.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.