Plone hotfix, 2015-09-10
This hotfix fixes multiple vulnerabilities in Plone.
This hotfix should be applied to the following versions of Plone:
# Plone 5.0rc1 and any version prior * Plone 4.3.6 and any version prior * Any older version of Plone including 2.1, 2.5, 3.0, 3.1, 3.2, 3.3, 4.0, 4.1, and 4.2
The hotfix is officially supported by the Plone security team on the following versions of Plone in accordance with the Plone version support policy: 3.3.6, 4.1.6, 4.2.7, 4.3.6 and 5.0rc1. However it has also received some testing on older versions of Plone. The fixes included here will be incorporated into subsequent releases of Plone, so Plone 4.3.7, 5.0rc2 and greater should not require this hotfix.
Installation
Installation instructions can be found at https://plone.org/products/plone-hotfix/releases/20150910
Q&A
- Q: How can I confirm that the hotfix is installed correctly and my site is protected?
A: On startup, the hotfix will log a number of messages to the Zope event log that look like this:
2015-09-10 03:20:08 INFO Products.PloneHotfix20150910 Applied addMember patch
The exact list of patches attempted depends on the version of Plone. If a patch is attempted but fails, it will be logged as a warning that says “Could not apply”. This may indicate that you have a non-standard Plone installation.
- Q: How can I report problems installing the patch?
A: Contact the Plone security team at security@plone.org, or visit the #plone channel on freenode IRC.
- Q: How can I report other potential security vulnerabilities?
A: Please email the security team at security@plone.org rather than discussing potential security issues publicly.
Changelog
1.1 (2015-09-10)
Update release information to not include “arbitrary code execution and privilege escalation” wording as there are no patches related to that here. Bad copy, paste from last patch.
If you have version 1.0, there is no reason to upgrade to 1.1. This release is just to update the readme shipped with the hotfix. [vangheem]
1.0 (2015-09-10)
Initial release
1 maintainer
Metadata
1 maintainer
Release files for Products.PloneHotfix20150910 1.1
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.PloneHotfix20150910-1.1.zip | 20.1 kB | Without provenance | Details for Products.PloneHotfix20150910-1.1.zip |
Release files / Products.PloneHotfix20150910-1.1.zip
| Download URL | Products.PloneHotfix20150910-1.1.zip |
|---|---|
| Size | 20.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
801a1da6217f92d2c89f30cba8df35641c6edb8e5179db10e09ee66398004ec6
|
|
BLAKE2b-256 checksum How to use checksums |
7367928f1fe4b4b73c62aa80d4b3270d9e984f39cb7c5d9b39fe9ad54deb7367
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for Products.PloneHotfix20150910 1.1
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.
