vulnerability / NVI-00013177 / Revision 1
plone.app.contenttypes has a Denial of Service in File Upload due to excessive filename length
GitHub lists this reviewed advisory for plone.app.contenttypes, plone.app.contenttypes, plone.app.contenttypes. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.
This report has not inspected your inventory, configuration, deployed build, reachability or evidence. A catalog listing and a severity score do not establish exposure or compromise.
01 / Meaning
Why it matters
Published affected context helps an owner decide what evidence to gather. This report has not examined your application.
6.5 medium
GitHub source severity; exploitability and local consequence require separate evidence.
As of · GitHub Advisory Database
02 / Applicability
The affected context
Affected versions, configuration prerequisites and known exclusions are public. Confirm each one against the deployed service.
plone.app.contenttypes
source listed= 5.0.0
### 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.
plone.app.contenttypes
source listed>= 4.0.0, <= 4.0.9
### 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.
plone.app.contenttypes
source listed<= 3.0.11
### 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.
03 / Response
What to do next
- investigate
Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.
Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system. GitHub Advisory Database
A fixed release is not deployment evidence.
Check current vendor support and compatibility. After making a change, verify the deployed build and relevant runtime conditions. Keep the evidence, owner and time. An updated lockfile alone does not prove what is running.
04 / Limits
What this report cannot establish
- Customer inventory, deployment, reachability and exploitation have not been inspected.
05 / Provenance
Sources you can inspect
Each assertion retains its source. Mirrored records may repeat one underlying publisher; additional links are not independent corroboration.
- GHSA-8pcw-h6w9-h46g ↗
GitHub Advisory Database · vendor advisory
Observed . GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.
Public revision history
Only published revisions appear here. Routine fetches do not create a material-change event.
- Revision 1 ·
First indexed by Null; source disclosure date is shown separately.