Skip to main content

Various Plone hotfixes, 2017-11-28

Project description

Plone hotfix, 2017-11-28

This hotfix fixes several security issues:

  • An open redirection and reflected Cross Site Scripting attack (XSS) on the login form and possibly other places where redirects are done. The isURLInPortal check that is done to avoid linking to an external site could be tricked into accepting malicious links.

  • An open redirection when calling a specific url.

  • Cross Site Scripting using the home_page member property.

  • Accessing private content via str.format in through-the-web templates and scripts. See this blog post by Armin Ronacher for the general idea. This improves an earlier hotfix. Since the format method was introduced in Python 2.6, this part of the hotfix is only relevant for Plone 4 and 5, not Plone 3.

Compatibility

This hotfix should be applied to the following versions of Plone:

  • Plone 5.0.9 and any earlier 5.x version

  • Plone 4.3.15 and any earlier 4.x version

The hotfix is officially supported by the Plone security team on the following versions of Plone in accordance with the Plone version support policy: 4.0.10, 4.1.6, 4.2.7, 4.3.15 and 5.0.9. However it has also received some testing on older versions of Plone, for example earlier 4.3 versions. The fixes included here will be incorporated into subsequent releases of Plone, so Plone 4.3.16, 5.0.10 and greater should not require this hotfix.

Installation

Installation instructions can be found at https://plone.org/security/hotfix/20171128

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:

2017-11-28 08:42:11 INFO Products.PloneHotfix20171128 Applied in_portal patch
2017-11-28 08:42:11 INFO Products.PloneHotfix20171128 Hotfix installed

The exact number of patches applied, will differ depending on what packages you are using. 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.0 (2017-11-28)

  • Initial release

Project details


Release history Release notifications | RSS feed

This version

1.0

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

Products.PloneHotfix20171128-1.0.tar.gz (13.1 kB view details)

Uploaded Source

File details

Details for the file Products.PloneHotfix20171128-1.0.tar.gz.

File metadata

File hashes

Hashes for Products.PloneHotfix20171128-1.0.tar.gz
Algorithm Hash digest
SHA256 b4f310edfd2da1d99c9e26c80b5913604ea860f00f53aca4f93799d3d7ee3280
MD5 baa3cc95cd297f9aeda387d0c8553292
BLAKE2b-256 fdea9e0248bbd9fb10fc9e671c90eb6b190c00fa0f9208858ee61d3019fc322a

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page