Categories
CVE-2021-21377

Open Redirect in omero-web (CVE-2021-21377)

Summary

Vulnerability in omero-web (CVE-2021-21377). Confidential information can be exposed externally. Exploitable via omero.web.redirect_allowed_hosts. Mitigation: upgrade to 5.9.0 or later.

Original description

The description as published by the source.

Background

OMERO.web supports redirection to a given URL after performing login or switching the group context. These URLs are not validated, allowing redirection to untrusted sites. OMERO.web 5.9.0 adds URL validation before redirecting. External URLs are not considered valid, unless specified in the omero.web.redirect_allowed_hosts setting.

Impact

OMERO.web before 5.9.0

Patches

5.9.0

Workarounds

No workaround

References

For more information

If you have any questions or comments about this advisory:

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-21377 has been found in omero-web.
Attackers can target a specific entry point like omero.web.redirect_allowed_hosts over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade omero-web to 5.9.0 or later.
If unsure, ask your IT team or search "omero-web CVE-2021-21377" on the vendor's site.

CVE-2021-21377 (omero-web) — CWE-601
Attack vector: remote (network-reachable)
Attack surface: omero.web.redirect_allowed_hosts
Patched: 5.9.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.

❓ What is the problem

A vulnerability (CWE-601) exists in omero-web. Attackers reach the vulnerable code path via omero.web.redirect_allowed_hosts.

📍 Affected scope

Check the vendor advisory for the affected versions of omero-web. Attack surface: omero.web.redirect_allowed_hosts.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 5.9.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'omero-web' . 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

  1. 1
    Identify exposure identify
    grep -r 'omero-web' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で omero-web を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade omero-web to 5.9.0

    ステージング環境で 5.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI omero-web
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.9.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details