# CVE-2017-1000484: Plone Open Redirect

> Attackers can redirect users to malicious sites via crafted URLs, potentially facilitating phishing attacks after login.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Jan 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xvwv-6wvx-px9x, PYSEC-2018-73

## What is CVE-2017-1000484?

CVE-2017-1000484 is a medium-severity vulnerability in Plone Plone, published on 3 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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. (The specific url can be seen by inspecting the hotfix code, but we don't want to make it too easy for attackers by spelling it out here.)

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2017-1000484?

5 open source packages ship an affected version, including plone and Plone. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `plone` | PyPI | From 2.5 | 4.3.16 |
| `plone` | PyPI | From 2.5 | 5.1.0 |
| `plone` | PyPI | From 5.0.0 | 5.1.0 |
| `Plone` | PyPI | From 2.5 | 4.3.16 |
| `Plone` | PyPI | From 5.0.0 | 5.1.0 |

Products: Plone Plone.

## How do I fix CVE-2017-1000484?

Upgrade plone to a fixed version for your release line: 4.3.16 or 5.1.0.

## Is CVE-2017-1000484 being exploited?

There is no known exploitation of CVE-2017-1000484 in the wild and no public exploit code.

## Other vulnerabilities in Plone Plone

- [CVE-2021-33509](https://insights.sbomify.com/CVE-2021-33509/): Incorrect Permission Assignment for Critical Resource in Plone (critical 9.9)
- [CVE-2020-35190](https://insights.sbomify.com/CVE-2020-35190/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-7941](https://insights.sbomify.com/CVE-2020-7941/): Plone Unauthenticated Write Vulnerability (critical 9.8)
- [CVE-2011-3587](https://insights.sbomify.com/CVE-2011-3587/): Zope Command Execution Vulnerability (critical 9.3)
- [CVE-2021-33926](https://insights.sbomify.com/CVE-2021-33926/): Server-Side Request Forgery in Plone CMS (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000484 and fix it if it is affected.

What it is: CVE-2017-1000484 is a medium-severity vulnerability in Plone Plone, published on 3 Jan 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-1000484 in the wild and no public exploit code.

Affected packages and fixed versions:
- plone (PyPI): affected from 2.5; fixed in 4.3.16
- plone (PyPI): affected from 2.5; fixed in 5.1.0
- plone (PyPI): affected from 5.0.0; fixed in 5.1.0
- Plone (PyPI): affected from 2.5; fixed in 4.3.16
- Plone (PyPI): affected from 5.0.0; fixed in 5.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-1000484/ (Markdown: https://insights.sbomify.com/CVE-2017-1000484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-1000484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-1000484
- OSV: https://osv.dev/vulnerability/CVE-2017-1000484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-1000484/
Summaries are generated and may contain mistakes; the official description above is the record.