pysec-2018-70
Vulnerability from pysec
Published
2018-01-03 18:29
Modified
2021-08-25 04:30
Details
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.
Impacted products
| Name | purl | plone | pkg:pypi/plone |
|---|
Aliases
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "plone",
"purl": "pkg:pypi/plone"
},
"ranges": [
{
"events": [
{
"introduced": "2.5"
},
{
"fixed": "4.3.16"
},
{
"introduced": "5"
},
{
"fixed": "5.1.0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"3.2",
"3.2.1",
"3.2.2",
"3.2.3",
"3.2a1",
"3.2rc1",
"3.3",
"3.3.1",
"3.3.2",
"3.3.3",
"3.3.4",
"3.3.5",
"3.3.6",
"3.3b1",
"3.3rc1",
"3.3rc2",
"3.3rc3",
"3.3rc4",
"3.3rc5",
"4.0",
"4.0.1",
"4.0.10",
"4.0.2",
"4.0.3",
"4.0.4",
"4.0.5",
"4.0.6",
"4.0.7",
"4.0.8",
"4.0.9",
"4.0a1",
"4.0a2",
"4.0a3",
"4.0a4",
"4.0a5",
"4.0b1",
"4.0b2",
"4.0b3",
"4.0b4",
"4.0b5",
"4.0rc1",
"4.1",
"4.1.1",
"4.1.2",
"4.1.3",
"4.1.4",
"4.1.5",
"4.1.6",
"4.1a1",
"4.1a2",
"4.1a3",
"4.1b1",
"4.1b2",
"4.1rc2",
"4.1rc3",
"4.2",
"4.2.1",
"4.2.2",
"4.2.3",
"4.2.4",
"4.2.5",
"4.2.6",
"4.2.7",
"4.2a1",
"4.2a2",
"4.2b1",
"4.2b2",
"4.2rc1",
"4.2rc2",
"4.3",
"4.3.1",
"4.3.10",
"4.3.11",
"4.3.12",
"4.3.13",
"4.3.14",
"4.3.15",
"4.3.2",
"4.3.3",
"4.3.4",
"4.3.5",
"4.3.6",
"4.3.7",
"4.3.8",
"4.3.9",
"4.3a1",
"4.3a2",
"4.3b1",
"4.3b2",
"4.3rc1",
"5.0",
"5.0.1",
"5.0.10",
"5.0.2",
"5.0.3",
"5.0.4",
"5.0.5",
"5.0.6",
"5.0.7",
"5.0.8",
"5.0.9",
"5.1a1",
"5.1a2",
"5.1b1",
"5.1b2",
"5.1b3",
"5.1b4",
"5.1rc1",
"5.1rc2"
]
}
],
"aliases": [
"CVE-2017-1000481"
],
"details": "When you visit a page where you need to login, Plone 2.5-5.1rc1 sends you to the login form with a \u0027came_from\u0027 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.",
"id": "PYSEC-2018-70",
"modified": "2021-08-25T04:30:16.749835Z",
"published": "2018-01-03T18:29:00Z",
"references": [
{
"type": "WEB",
"url": "https://plone.org/security/hotfix/20171128/open-redirection-on-login-form"
}
]
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.
Loading…
Loading…