CVE-2017-1000481
Last modified
CVE-2017-1000481 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.69% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Plone | Plone | 2.5.5 | — |
| Plone | Plone | 3.3 | — |
| Plone | Plone | 3.3.1 | — |
| Plone | Plone | 3.3.2 | — |
| Plone | Plone | 3.3.3 | — |
| Plone | Plone | 3.3.4 | — |
| Plone | Plone | 3.3.5 | — |
| Plone | Plone | 3.3.6 | — |
| Plone | Plone | 4.0 | — |
| Plone | Plone | 4.0.1 | — |
| Plone | Plone | 4.0.2 | — |
| Plone | Plone | 4.0.3 | — |
| Plone | Plone | 4.0.4 | — |
| Plone | Plone | 4.0.5 | — |
| Plone | Plone | 4.0.7 | — |
| Plone | Plone | 4.0.8 | — |
| Plone | Plone | 4.0.9 | — |
| Plone | Plone | 4.0.10 | — |
| Plone | Plone | 4.1 | — |
| Plone | Plone | 4.1.1 | — |
| Plone | Plone | 4.1.2 | — |
| Plone | Plone | 4.1.3 | — |
| Plone | Plone | 4.1.4 | — |
| Plone | Plone | 4.1.5 | — |
| Plone | Plone | 4.1.6 | — |
| Plone | Plone | 4.2 | — |
| Plone | Plone | 4.2.1 | — |
| Plone | Plone | 4.2.2 | — |
| Plone | Plone | 4.2.3 | — |
| Plone | Plone | 4.2.4 | — |
| Plone | Plone | 4.2.5 | — |
| Plone | Plone | 4.2.6 | — |
| Plone | Plone | 4.2.7 | — |
| Plone | Plone | 4.3 | — |
| Plone | Plone | 4.3.1 | — |
| Plone | Plone | 4.3.2 | — |
| Plone | Plone | 4.3.3 | — |
| Plone | Plone | 4.3.4 | — |
| Plone | Plone | 4.3.5 | — |
| Plone | Plone | 4.3.6 | — |
| Plone | Plone | 4.3.7 | — |
| Plone | Plone | 4.3.8 | — |
| Plone | Plone | 4.3.9 | — |
| Plone | Plone | 4.3.10 | — |
| Plone | Plone | 4.3.11 | — |
| Plone | Plone | 4.3.12 | — |
| Plone | Plone | 4.3.14 | — |
| Plone | Plone | 4.3.15 | — |
| Plone | Plone | 5.0 | — |
| Plone | Plone | 5.0.1 | — |
Showing 50 of 59 affected configurations. See NVD for the full list.
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-1000481?
How severe is CVE-2017-1000481?
How do I fix CVE-2017-1000481?
Are you affected by CVE-2017-1000481?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
