Categories
CVE-2021-21392

Open Redirect in matrix-synapse (CVE-2021-21392)

Summary

Vulnerability in matrix-synapse (CVE-2021-21392). Data can be tampered with by attackers. Mitigation: upgrade to 1.28.0rc1 or later.

Original description

The description as published by the source.

Synapse is a Matrix reference homeserver written in python (pypi package matrix-synapse). Matrix is an ecosystem for open federated Instant Messaging and VoIP. In Synapse before version 1.28.0 requests to user provided domains were not restricted to external IP addresses when transitional IPv6 addresses were used. Outbound requests to federation, identity servers, when calculating the key validity for third-party invite events, sending push notifications, and generating URL previews are affected. This could cause Synapse to make requests to internal infrastructure on dual-stack networks. See referenced GitHub security advisory for details and workarounds.

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-21392 has been found in matrix-synapse.
Data can be tampered with by attackers.
What to do: upgrade matrix-synapse to 1.28.0rc1 or later.
If unsure, ask your IT team or search "matrix-synapse CVE-2021-21392" on the vendor's site.

CVE-2021-21392 (matrix-synapse) — CWE-601
Attack vector: remote (network-reachable)
Patched: 1.28.0rc1 — 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 matrix-synapse.

📍 Affected scope

Check the vendor advisory for the affected versions of matrix-synapse.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 1.28.0rc1.

🛡️ 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 'matrix-synapse' . 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 'matrix-synapse' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade matrix-synapse to 1.28.0rc1

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

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

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

Affected packages

PyPI matrix-synapse
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.28.0rc1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

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