Plone Hotfix package, 2011-10-04
This hotfix fixes the following vulnerabilities:
A vulnerability in CMFEditions where KwAsAttributes classes were publishable, exposing sub-objects to anonymous access. This vulnerability is found in CMFEditions 2.0a1 and up. CMFEditions 1.x and before are not vulnerable.
Zope vulnerability CVE 2011-3587. This vulnerability is found in Zope 2.12.x and 2.13.x. Zope 2.11 and before are not vulnerable.
This Plone Hotfix applies the same fix as Products.Zope_Hotfix_CVE_2011_3587 and can co-exist with that patch.
This hotfix is supported on Plone 4.0 - 4.0.9, 4.1 and 4.2. Older versions of Plone (3.3.x and below) are not affected by the vulnerabilities and are not supported by this patch.
The fixes included here will be incorporated into subsequent releases of Plone, so Plone 4.0.10, 4.1.1, 4.2a3 and greater should not require this hotfix.
Installation
Installation instructions can be found at http://plone.org/products/plone-hotfix/releases/20111004
Changelog
1.0 (2011-10-04)
Initial release [Plone security team]
1 maintainer
Metadata
1 maintainer
Release files for Products.PloneHotfix20110928 1.0
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.PloneHotfix20110928-1.0.zip | 6.8 kB | Without provenance | Details for Products.PloneHotfix20110928-1.0.zip |
Release files / Products.PloneHotfix20110928-1.0.zip
| Download URL | Products.PloneHotfix20110928-1.0.zip |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0ff27dc4d4befd31c2891f852bdd5b747d1b2197e25a753212b5e0e0776262eb
|
|
BLAKE2b-256 checksum How to use checksums |
373feb0058f29ab4d135b0bd5e66dbe09e1ba27eac306b5a8d9859f7db6cd8a9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.PloneHotfix20110928 1.0
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.
