Categories
CVE-2021-41176

Cross-Site Request Forgery (CSRF) in pterodactyl/panel (CVE-2021-41176)

Summary

Vulnerability in pterodactyl/panel (CVE-2021-41176). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.6.3 or later.

Original description

The description as published by the source.

Pterodactyl is an open-source game server management panel built with PHP 7, React, and Go. In affected versions of Pterodactyl a malicious user can trigger a user logout if a signed in user visits a malicious website that makes a request to the Panel's sign-out endpoint. This requires a targeted attack against a specific Panel instance, and serves only to sign a user out. No user details are leaked, nor is any user data affected, this is simply an annoyance at worst. This is fixed in version 1.6.3.

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-41176 has been found in pterodactyl/panel.
Risk of unauthorized operations or information disclosure.
What to do: upgrade pterodactyl/panel to 1.6.3 or later.
If unsure, ask your IT team or search "pterodactyl/panel CVE-2021-41176" on the vendor's site.

CVE-2021-41176 (pterodactyl/panel) — CWE-352
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.6.3 — 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

CSRF (CWE-352) exists in pterodactyl/panel.

📍 Affected scope

Check the vendor advisory for the affected versions of pterodactyl/panel.

🔥 Severity

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

🔧 How to fix

Update to 1.6.3.

🛡️ 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 'pterodactyl/panel' . 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 'pterodactyl/panel' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade pterodactyl/panel to 1.6.3

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

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

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

Affected packages

Packagist pterodactyl/panel
[{"type":"ECOSYSTEM","events":[{"introduced":"1.0.0"},{"fixed":"1.6.3"}]}]

References

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