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 A url /login?camefrom=////evil.example may redirect to an external website after login. Standard Plone is not affected, but if you have customised the login, for example with add-ons, you might be affected. You can try the url to check if you are affected or not. Patches The problem has been patched in Products.isurlinportal. Plone 6.2: upgrade to Products.isurlinportal 4.0.0. Plone 6.1: upgrade to Products.isurlinportal 3.1.0. Plone 6.0: upgrade to Products.isurlinportal 2.1.0. Older Plone versions don't have security support anymore. Workarounds There are no known workarounds. Background When you are anonymous and land on a page that requires a login, Plone sends you to the login form. After successful login, Plone redirects you back to the page you came from. Various other forms and pages have a similar system. This could get abused by an attacker to trick Plone into redirecting to a different website. Plone checks the page that would be redirected to. It is only accepted…
Recommended action: Upgrade to 4.0.0, 3.1.0 or 2.1.0 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact Various parts of Plone use the 'is url in portal' check for security, mostly to see if it is safe to redirect to a url. A url like https://example.org is not in the portal. But the url https:example.org without slashes tricks our code and it is considered to be in the portal. When redirecting, some browsers go to https://example.org, others give an error. Attackers may use this to redirect you to their site, especially as part of a phishing attack. Patches The problem has been patched in Products.isurlinportal 1.2.0. This is a recommended upgrade for all users of Plone 4.3 and 5, on Python 2.7 or higher. It has not been tested on earlier Plone or Python versions. Upcoming Plone 5.2.5 and higher will include the new version. Discovered This vulnerability was discovered and reported by Yuji Tounai of Mitsui Bussan Secure Directions, Inc. Thank you! For more information If you have any questions or comments about this advisory: Email the Plone Security Team at security@plone.org,…
Recommended action: Upgrade to 1.2.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.