CVE-2017-1000484
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedBy 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.)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePlone 2.5-5.1rc1 contains an open redirect vulnerability via a specific URL parameter. An attacker can craft a malicious link that, after a user logs into the Plone login form and gets redirected to the specific URL, results in a second redirect to the attacker's website, enabling phishing attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.5.5= 3.3= 3.3.1= 3.3.2= 3.3.3= 3.3.4= 3.3.5= 3.3.6= 4.0= 4.0.1= 4.0.2= 4.0.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Plone versionLocate the version file or admin interface. Common paths: check the 'versions.cfg' or 'plone.app.versioning' admin panel, or look at the Plone control panel under 'Version'.Affected if Version matches or falls within: 2.5.5, 3.3, 3.3.1-3.3.6, 4.0-4.0.3 (or any version from 2.5 through 5.1rc1)
-
Confirm login form is accessibleAccess the Plone login page (typically /login_form or /login) to verify the authentication module is enabled and in use.Affected if Login form is active and accepts user authentication
-
Inspect login redirect behaviorSubmit a login with a 'next' or 'redirect' URL parameter pointing to an external domain (for example, ?next=http://attacker.com). Observe whether the application redirects to the external site after authentication.Affected if After login, the application redirects to the external domain specified in the URL parameter rather than rejecting it or restricting to internal paths only
-
Check for the hotfix patchSearch for the file 'CVE-2017-1000484' hotfix or check Plone's hotfix registry at plone.org. Look for a file named 'plone-5.1.1-hotfix.patch' or similar in the products directory.Affected if No hotfix is installed and the Plone version is within the affected range, enabling the open redirect behavior
If your Plone version is between 2.5 and 5.1rc1 and the login form permits arbitrary external URLs in the redirect parameter after authentication, you are affected by this open redirect vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply the Plone hotfix for CVE-2017-1000484 or upgrade to a patched Plone version. Verify that login redirects only permit trusted internal paths.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000484 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-1000484 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data