Open Redirect in products-isurlinportal (CVE-2021-32806)
Summary
Vulnerability in products-isurlinportal (CVE-2021-32806). Data can be tampered with by attackers. Exploitable via Products.isurlinportal. Mitigation: upgrade to 1.2.0 or later.
Original description
The description as published by the source.
Impact
Various parts of Plone use the 'is url in portal' check for security, mostly to see if it is safe to redirect to a url. A url like https://example.org is not in the portal.
But the url https:example.org without slashes tricks our code and it is considered to be in the portal.
When redirecting, some browsers go to https://example.org, others give an error.
Attackers may use this to redirect you to their site, especially as part of a phishing attack.
Patches
The problem has been patched in Products.isurlinportal 1.2.0.
This is a recommended upgrade for all users of Plone 4.3 and 5, on Python 2.7 or higher.
It has not been tested on earlier Plone or Python versions.
Upcoming Plone 5.2.5 and higher will include the new version.
Discovered
This vulnerability was discovered and reported by Yuji Tounai of Mitsui Bussan Secure Directions, Inc. Thank you!
For more information
If you have any questions or comments about this advisory:
- Email the Plone Security Team at security@plone.org, especially when you think you have discovered a security problem or when you are not sure.
- Open an issue in the tracker if your question or comment can be public.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-32806 has been found in products-isurlinportal.
Attackers can target a specific entry point like Products.isurlinportal over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade products-isurlinportal to 1.2.0 or later.
If unsure, ask your IT team or search "products-isurlinportal CVE-2021-32806" on the vendor's site.
CVE-2021-32806 (products-isurlinportal) — CWE-601
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Products.isurlinportal
Patched: 1.2.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-601) exists in products-isurlinportal. Attackers reach the vulnerable code path via Products.isurlinportal without authentication.
Check the vendor advisory for the affected versions of products-isurlinportal. Attack surface: Products.isurlinportal.
Severity: ?. Data can be tampered with by attackers.
Update to 1.2.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'products-isurlinportal' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'products-isurlinportal' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
products-isurlinportalを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade products-isurlinportal to 1.2.0ステージング環境で 1.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web jvn.jp