Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Impact When creating an Image or File with a very large filename, Plone can become unresponsive. Even if the content loads, it can be hard to edit or delete, because the UI is unwieldy. Patches The problem has been patched in plone.app.contenttypes. On Plone 6.2, upgrade to plone.app.contenttypes 5.0.1. On Plone 6.1, upgrade to plone.app.contenttypes 4.0.10. On Plone 6.0, upgrade to plone.app.contenttypes 3.0.12 Another part of this problem has been patched in plone.app.dexterity. See this advisory. Workarounds There are no known workarounds. This problem was responsibly reported by Aldin Visnjic to the Plone/Zope Security Team. Thank you! Note: The Plone/Zope Security team felt that the kind of fixes that were needed could be disruptive in corner cases if they were not careful. So they decided to develop the fixes publicly, giving the whole community the chance the review, and giving them the benefit from early feedback.
Recommended action: Upgrade to 5.0.1, 4.0.10 or 3.0.12 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact Plone is vulnerable to reflected cross site scripting and open redirect when an attacker can get a compromised version of the imageviewfullscreen page in a cache, for example in Varnish. The technique is known as cache poisoning. Any later visitor can get redirected when clicking on a link on this page. Usually only anonymous users are affected, but this depends on your cache settings. Patches New versions of plone.app.contenttypes have been released. Version 2.2.3 works on Plone 5.2 and will be included in Plone 5.2.7. Version 3.0.0a9 works on Plone 6 and will be included in Plone 6.0.0a3. Note that the Products.CMFPlone package has the same problem in the 4.3 series. In Plone 5.0-5.2, the default Products.ATContentTypes version has the same problem. See advisory. For all unpatched versions of the three packages, you can use the following workaround. Workaround Make sure the imageviewfullscreen page is not stored in the cache. In Plone: Login as Manager and go to Site Setup.…
Recommended action: Upgrade to 2.2.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.