Control panel only API response emulation replaces "securityKey" and reaches server RCE
Résumé
The app/process-api-response-headers action accepts fake Craft API response headers from any authenticated control panel user.
A non-admin user with only accessCp can place newline characters in X-Craft-Plugin-Licenses. Craft passes this value to its .env writer without removing the newlines....
Résumé IA
Rédigé par une IA externe ; il peut contenir des erreurs. Vérifiez la description d'origine et les références ci-dessous avant d'agir.
制御パネルに管理者以外でアクセスできる利用者が、偽のAPI応答ヘッダーとCRLF注入を使って暗号鍵を書き換え、サーバー上でコードを実行できる脆弱性です。影響を受けるのはCraft CMS 5.0.0以降5.11.2未満および4.0.0以降4.18.9未満です。5.11.2または4.18.9以降へ更新してください。
Paquets affectés
| Écosystème | Paquet | Concernées | Corrigé |
|---|---|---|---|
| craftcms | cms |
≥ 5.0.0, < 5.11.2 ≥ 4.0.0, < 4.18.9 |
5.11.2 4.18.9 |
Description d'origine La description telle que publiée par la source (souvent en anglais).
The app/process-api-response-headers action accepts fake Craft API response headers from any authenticated control panel user.
A non-admin user with only accessCp can place newline characters in X-Craft-Plugin-Licenses. Craft passes this value to its .env writer without removing the newlines.
This lets the user insert a new attacker-known CRAFT_SECURITY_KEY into .env. After Craft loads that key, the user can forge a signed login redirect containing a Twig system() callback.
This is different from the previous report. That report reads the existing key through a Twig sandbox bypass. This report replaces the key through fake API headers and CRLF injection. Fixing either source does not fix the other.
Source: CVE.org (CVE Program・cvelistV5) NVD
Références
- web hckrt.com
- web github.com
- web github.com
- web github.com