提出 #901836: liufee feehi cms 2.1.1 配置错误情報

タイトルliufee feehi cms 2.1.1 配置错误
説明FeehiCMS 2.1.1 ships with an empty cookieValidationKey in all environment templates, including production (environments/prod/backend/config/main-local.php and environments/prod/frontend/config/main-local.php). The Yii2 framework uses this key to sign cookies via HMAC-SHA256. An empty key allows attackers to forge any Yii2-managed cookie, including identity cookies (when enableAutoLogin is enabled) and CSRF tokens. The docker-entrypoint.sh init script does not auto-generate a random key, so Docker deployments use the empty key by default. Impact: Cookie integrity failure, potential authentication bypass, CSRF protection bypass. Proof of Concept (theoretical): An attacker can compute HMAC-SHA256(cookie_value, '') to forge a valid Yii2 cookie because the key is empty. Remediation: Auto-generate a random 32-byte key during init, add empty-key detection at startup, generate key in Docker entrypoint. References: - https://github.com/liufee/cms - https://github.com/liufee/cms/issues/96 - Full report: https://github.com/yang5ynag/cve/blob/main/FEHI-003-Empty-cookieValidationKey.md
ユーザー
 lyang (UID 100042)
送信2026年07月22日 08:25 (2 月 ago)
モデレーション2026年09月06日 10:59 (2 months later)
ステータス承諾済み
VulDBエントリ399398 [liufee FeehiCMS 迄 2.1.1 Cookie Validation main-local.php cookieValidationKey 弱い暗号化]
ポイント17

Do you want to use VulDB in your project?

Use the official API to access entries easily!