First published: Wed Jan 03 2018(Updated: )
When you visit a page where you need to login, Plone 2.5-5.1rc1 sends you to the login form with a 'came_from' parameter set to the previous url. After you login, you get redirected to the page you tried to view before. An attacker might try to abuse this by letting you click on a specially crafted link. You would login, and get redirected to the site of the attacker, letting you think that you are still on the original Plone site. Or some javascript of the attacker could be executed. Most of these types of attacks are already blocked by Plone, using the `isURLInPortal` check to make sure we only redirect to a page on the same Plone site. But a few more ways of tricking Plone into accepting a malicious link were discovered, and fixed with this hotfix.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/Plone | >=5<5.1.0 | 5.1.0 |
pip/Plone | >=2.5<4.3.16 | 4.3.16 |
pip/Products.CMFPlone | >=5.1a1<5.1.0 | 5.1.0 |
pip/Products.CMFPlone | >=5.0.0<5.0.10 | 5.0.10 |
pip/Products.CMFPlone | <4.3.17 | 4.3.17 |
Plone CMS | =2.5.5 | |
Plone CMS | =3.3 | |
Plone CMS | =3.3.1 | |
Plone CMS | =3.3.2 | |
Plone CMS | =3.3.3 | |
Plone CMS | =3.3.4 | |
Plone CMS | =3.3.5 | |
Plone CMS | =3.3.6 | |
Plone CMS | =4.0 | |
Plone CMS | =4.0.1 | |
Plone CMS | =4.0.2 | |
Plone CMS | =4.0.3 | |
Plone CMS | =4.0.4 | |
Plone CMS | =4.0.5 | |
Plone CMS | =4.0.7 | |
Plone CMS | =4.0.8 | |
Plone CMS | =4.0.9 | |
Plone CMS | =4.0.10 | |
Plone CMS | =4.1 | |
Plone CMS | =4.1.1 | |
Plone CMS | =4.1.2 | |
Plone CMS | =4.1.3 | |
Plone CMS | =4.1.4 | |
Plone CMS | =4.1.5 | |
Plone CMS | =4.1.6 | |
Plone CMS | =4.2 | |
Plone CMS | =4.2.1 | |
Plone CMS | =4.2.2 | |
Plone CMS | =4.2.3 | |
Plone CMS | =4.2.4 | |
Plone CMS | =4.2.5 | |
Plone CMS | =4.2.6 | |
Plone CMS | =4.2.7 | |
Plone CMS | =4.3 | |
Plone CMS | =4.3.1 | |
Plone CMS | =4.3.2 | |
Plone CMS | =4.3.3 | |
Plone CMS | =4.3.4 | |
Plone CMS | =4.3.5 | |
Plone CMS | =4.3.6 | |
Plone CMS | =4.3.7 | |
Plone CMS | =4.3.8 | |
Plone CMS | =4.3.9 | |
Plone CMS | =4.3.10 | |
Plone CMS | =4.3.11 | |
Plone CMS | =4.3.12 | |
Plone CMS | =4.3.14 | |
Plone CMS | =4.3.15 | |
Plone CMS | =5.0 | |
Plone CMS | =5.0-rc1 | |
Plone CMS | =5.0-rc2 | |
Plone CMS | =5.0-rc3 | |
Plone CMS | =5.0.1 | |
Plone CMS | =5.0.2 | |
Plone CMS | =5.0.3 | |
Plone CMS | =5.0.4 | |
Plone CMS | =5.0.5 | |
Plone CMS | =5.0.6 | |
Plone CMS | =5.0.7 | |
Plone CMS | =5.0.8 | |
Plone CMS | =5.0.9 | |
Plone CMS | =5.1-a1 | |
Plone CMS | =5.1-a2 | |
Plone CMS | =5.1-b2 | |
Plone CMS | =5.1-b3 | |
Plone CMS | =5.1-b4 | |
Plone CMS | =5.1-rc1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2017-1000481 is classified as medium due to the potential for an open redirect attack.
To fix CVE-2017-1000481, upgrade to Plone version 5.1.0, 5.0.10, or 4.3.17.
CVE-2017-1000481 affects Plone versions 2.5.5 to 5.1-rc1, including various versions in between.
CVE-2017-1000481 allows attackers to perform open redirect attacks through manipulation of the 'came_from' parameter.
Authentication is not compromised in CVE-2017-1000481, but it can lead users to unintended malicious sites after login.