Pterodactyl's improper JWT scoping allows subuser to upload files when not explicitly granted `file.create` permissions
pterodactyl panel
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| pterodactyl/panel Packagist |
|
|
| github.com/pterodactyl/wings Go |
|
|
pterodactyl panel
| Product | Affected | Fixed in |
|---|---|---|
| pterodactyl/panel Packagist |
|
|
| github.com/pterodactyl/wings Go |
|
|
Pterodactyl is a free, open-source game server management panel. Prior to Panel version 1.12.3 and Wings version 1.12.2, the Wings /upload/file endpoint accepted any valid panel-signed JWT that contained server_uuid, user_uuid, and unique_id claims without checking the token's intended purpose; because the Panel issues JWTs carrying those same claims for lower-privilege operations such as WebSocket authentication and file-download links, an authenticated subuser could reuse one of those tokens (for example a WebSocket token obtained with only the websocket.connect permission) by replaying it against /upload/file to write arbitrary files to the same server, despite never being granted the file.create permission. This issue is fixed in Panel version 1.12.3 and Wings version 1.12.2.
From the CVE record · GitHub_M
Before Panel 1.12.3 and Wings 1.12.2, the Wings /upload/file endpoint accepted valid panel-signed JWTs without checking their intended purpose. An authenticated subuser could reuse a lower-privilege token to write arbitrary files to the same server without file.create permission.
Operators running pterodactyl/panel before 1.12.3 or github.com/pterodactyl/wings before 1.12.2 should check their installations.