Plone Hotfix for CVE 2011-0720
This is a critical security hotfix which should be applied to the following versions of Plone:
Plone 4 <= 4.0.3
Plone 3 <= 3.3.5
Any version of Plone 2.5, 2.1, or 2.0
This hotfix is not required for Plone >= 4.0.4.
Additional information about the hotfix including frequently asked questions is available at http://plone.org/products/plone/security/advisories/cve-2011-0720
This hotfix applies the following modifications to improve Plone security:
Applies security declarations to some methods that were missing them, in order to address the vulnerability identified in CVE 2011-0720. The vulnerability discussed there affects Plone 2.5 and greater.
Applies security declarations and removal of docstrings to some additional methods that were identified by the Plone security team in an audit following the identification of CVE 2011-0720. This includes some methods present in Plone 2.0 and 2.1.
If necessary, applies a patch to the ZPublisher to fix an issue with the checking of whether traversed methods are publishable. This issue affects Plone 3.0 and higher, and is also available in the following new Zope2 releases: 2.10.13, 2.11.8, 2.12.15, 2.13.4
Installation
Installation instructions can be found at http://plone.org/products/plone-hotfix/releases/CVE-2011-0720
Changelog
1.2 (2011-02-26)
Note: This release does not provide additional security compared to the 1.0 and 1.1 releases. It merely fixes an issue that prevented respecting placefully assigned roles in some cases. Therefore it is an optional upgrade unless you’ve experienced this issue.
Protect methods with PermissionRoles rather than hardcoded lists of roles, so that Zope will respect placeful assignments of roles to permissions. [davisagli]
Clarify the info that is printed on startup so that people don’t worry about the fact that their Zope versions wasn’t identified. [davisagli]
1.1 (2011-02-08)
Note: This release does not provide additional security compared to the 1.0 release. It merely fixes 2 installation issues. If 1.0 installed fine for you, you do not need to update.
Try 2 ways to delete the docstring as we had one report of the way we were using not working (thanks Andrew Mleczko for the report). [davisagli]
Fix issue with application to some recent revisions of Zope 2.10. Thanks to Ethan Jucovy for calling this to our attention. [davisagli]
1.0 (2011-02-08)
Initial release [Plone security team]
Metadata
Release files for Products.PloneHotfix20110720 1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| Products.PloneHotfix20110720-1.2.zip | 10.6 kB | Without provenance | Details for Products.PloneHotfix20110720-1.2.zip |
Release files / Products.PloneHotfix20110720-1.2.zip
| Download URL | Products.PloneHotfix20110720-1.2.zip |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
aa40b0bea88d3c4d201604c8b65ca12791bf6fd3fa9542694f1f2139cb247010
|
|
BLAKE2b-256 checksum How to use checksums |
cf17ed80608dfb3f22200d706250d55d0b044cb60c97a99426d42f4a2180260b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.PloneHotfix20110720 1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.