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
4 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Impact When creating content with a very large title or description field, 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.dexterity. On Plone 6.2, upgrade to plone.app.dexterity 5.0.1. On Plone 6.1, upgrade to plone.app.dexterity 4.1.3. On Plone 6.0, upgrade to plone.app.dexterity 3.2.3. Another part of this problem has been patched in plone.app.contenttypes. 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.1.3 or 3.2.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Plone before 5.2.3 allows XXE attacks via a feature that is protected by an unapplied permission of plone.schemaeditor.ManageSchemata (therefore, only available to the Manager role).
Recommended action: Upgrade to 2.6.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Plone before 5.2.3 allows SSRF attacks via the tracebacks feature (only available to the Manager role).
Recommended action: Upgrade to 2.6.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Plone before 5.2.3 allows XXE attacks via a feature that is explicitly only available to the Manager role.
Recommended action: Upgrade to 2.6.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.