Vulnerability in omero-web (CVE-2021-41132)
Summary
Vulnerability in omero-web (CVE-2021-41132). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 5.11.0 or later.
Original description
The description as published by the source.
OMERO.web provides a web based client and plugin infrastructure. In versions prior to 5.11.0, a variety of templates do not perform proper sanitization through HTML escaping. Due to the lack of sanitization and use of jQuery.html(), there are a whole host of cross-site scripting possibilities with specially crafted input to a variety of fields. This issue is patched in version 5.11.0. There are no known workarounds aside from upgrading.
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-41132 has been found in omero-web.
Risk of unauthorized operations or information disclosure.
What to do: upgrade omero-web to 5.11.0 or later.
If unsure, ask your IT team or search "omero-web CVE-2021-41132" on the vendor's site.
CVE-2021-41132 (omero-web) — CWE-116
Attack vector: remote (network-reachable) / unauthenticated
Patched: 5.11.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-116) exists in omero-web.
Check the vendor advisory for the affected versions of omero-web.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.11.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 '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
-
1Identify exposure identify
grep -r 'omero-web' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
omero-webを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade omero-web to 5.11.0ステージング環境で 5.11.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory openmicroscopy.org
- package github.com
- patch github.com
- web github.com
- web github.com
- web openmicroscopy.org