Due to improperly configured CSRF protections on two routes, a malicious user could execute a CSRF-based attack against the following endpoints:
At no point would any data be exposed to the malicious user, this would simply trigger email spam to an administrative user, or generate a single auto-deployment token unexpectedly. This token is not revealed to the malicious user, it is simply created unexpectedly in the system.
This has been addressed in https://github.com/pterodactyl/panel/commit/bf9cbe2c6d5266c6914223e067c56175de7fc3a5 which will be released as 1.6.6
.
Users may optionally manually apply the fixes released in v1.6.6 to patch their own systems.
{ "nvd_published_at": "2021-11-17T20:15:00Z", "github_reviewed_at": "2021-11-17T14:37:10Z", "severity": "MODERATE", "github_reviewed": true, "cwe_ids": [ "CWE-352" ] }