Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2021-32645

Open Redirect in hyn/multi-tenant (CVE-2021-32645)

Summary

Vulnerability in hyn/multi-tenant (CVE-2021-32645). Risk of unauthorized operations or information disclosure. Exploitable via force_https. Mitigation: upgrade to 5.7.2 or later.

Original description

The description as published by the source.

Impact

In some situations, it is possible to have open redirects where users can be redirected from your site to any other site using a specially crafted URL.
This is only the case for installations where the default Hostname Identification is used and the environment uses tenants that have force_https set to true (default: false)

Patches

Version 5.7.2 contains the relevant patches to fix this bug. Stripping the URL from special characters to prevent specially crafted URL's from being redirected to.

Workarounds

There is a simple way to work around the security issue

  • Set the force_https to every tenant to false

References

https://nvd.nist.gov/vuln/detail/CVE-2018-11784

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-32645 has been found in hyn/multi-tenant.
Attackers can target a specific entry point like force_https over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade hyn/multi-tenant to 5.7.2 or later.
If unsure, ask your IT team or search "hyn/multi-tenant CVE-2021-32645" on the vendor's site.

CVE-2021-32645 (hyn/multi-tenant) — CWE-601
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: force_https / true / false
Patched: 5.7.2 — 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 hyn/multi-tenant. Attackers reach the vulnerable code path via force_https without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of hyn/multi-tenant. Attack surface: force_https / true / false.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 5.7.2.

🛡️ 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 'hyn/multi-tenant' . 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 'hyn/multi-tenant' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade hyn/multi-tenant to 5.7.2

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

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

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

Affected packages

Packagist hyn/multi-tenant
[{"type":"ECOSYSTEM","events":[{"introduced":"5.6.0"},{"fixed":"5.7.2"}]}]

References

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