First published: Wed Jan 03 2018(Updated: )
By linking to a specific url in Plone 2.5-5.1rc1 with a parameter, an attacker could send you to his own website. On its own this is not so bad: the attacker could more easily link directly to his own website instead. But in combination with another attack, you could be sent to the Plone login form and login, then get redirected to the specific url, and then get a second redirect to the attacker website.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
pip/plone | >=5.0.0<5.1.0 | 5.1.0 |
pip/plone | >=4.0.0<4.3.16 | 4.3.16 |
pip/Plone | >=2.5<4.3.16 | 4.3.16 |
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.
CVE-2017-1000484 is categorized as a medium severity vulnerability.
To fix CVE-2017-1000484, update Plone to version 5.1.0 or 4.3.16.
CVE-2017-1000484 affects multiple versions of Plone, including versions from 2.5.5 to 5.1-rc1.
CVE-2017-1000484 is an open redirect vulnerability.
Yes, CVE-2017-1000484 can potentially be exploited for phishing attacks by redirecting users to malicious sites.