p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in plone-app-contenttypes

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für plone-app-contenttypes: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 3

  1. GHSA-8pcw-h6w9-h46g

    Mittel · CVSS 6.5Korrektur verfügbar

    plone.app.contenttypes has a Denial of Service in File Upload due to excessive filename length

    ### 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](https://github.com/plone/plone.app.dexterity/security/advisories/GHSA-5426-92w4-wvhv). ### Workarounds There are

    • Auf 3.0.12 aktualisieren
    • Auf 4.0.10 aktualisieren
    • Auf 5.0.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. GHSA-f7qw-5fgj-247x

    Mittel · CVSS 4.3Korrektur verfügbar

    Cross-site Scripting and Open Redirect in plone.app.contenttypes

    ### Impact Plone is vulnerable to reflected cross site scripting and open redirect when an attacker can get a compromised version of the image_view_fullscreen 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 p

    • Auf 2.2.3 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →