GHSA-5426-92w4-wvhv: Medium severity pip/plone.app.dexterity vulnerability
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/plone.app.dexterityto a version that resolves this vulnerability.Fixed in 3.2.3 - Upgrade
Upgrade
pip/plone.app.dexterityto a version that resolves this vulnerability.Fixed in 4.1.3 - Upgrade
Upgrade
pip/plone.app.dexterityto a version that resolves this vulnerability.Fixed in 5.0.1 - Upgrade
Upgrade
plone.app.dexterityto a version that resolves this vulnerability.Fixed in 3.2.3 - Upgrade
Upgrade
plone.app.dexterityto a version that resolves this vulnerability.Fixed in 4.1.3 - Upgrade
Upgrade
plone.app.dexterityto a version that resolves this vulnerability.Fixed in 5.0.1
Event History
Frequently Asked Questions
What access does an attacker need to trigger the availability impact?
The CVSS vector indicates that exploitation is network-reachable, requires low privileges, and does not require user interaction. An attacker would need the ability to create content with a very large title or description field.
Which fixed plone.app.dexterity versions should be deployed?
For Plone 6.2, upgrade to plone.app.dexterity 5.0.1. For Plone 6.1, upgrade to 4.1.3; for Plone 6.0, upgrade to 3.2.3.
Is there a mitigation if an immediate upgrade is not possible?
No known workarounds are available. The advisory identifies upgrading plone.app.dexterity as the remediation.
Does fixing plone.app.dexterity address every related issue?
No. The advisory states that another part of the problem was patched separately in plone.app.contenttypes and refers to GHSA-8pcw-h6w9-h46g.