Pterodactyl critical vulnerability #135
prplwtf
announced in
Sticky board
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Important
This vulnerability is part of Pterodactyl, our upstream's codebase. The vulnerable files in question are not edited by Blueprint, updating Pterodactyl is sufficient to patch your installation.
Hi all,
Pterodactyl released
1.11.11
, which fixes a critical security vulnerability. You are advised to patch/update your panel immediately. Below are instructions on how to do so.Patching your panel (recommended)
Run the following commands, replace
/var/www/pterodactyl
with your Pterodactyl path.Note that this patch will not update your panel's version to latest, that's fine though, ignore.
Restoring Blueprint after updating Pterodactyl
If you happened to have updated Pterodactyl instead of patching it, you might find yourself with a half-borked installation of Blueprint. This is normal, you just need to run a couple commands and you'll be back up in no time.
blueprint -upgrade
. It will ask for confirmation and show a couple warnings, don't worry, extension configurations will not be lost.<extension>.blueprint
files, download them again.blueprint -install *.blueprint
in your Pterodactyl directory to install all available extensions at once.Updating Blueprint Docker
Running Blueprint Docker? Read more about upgrading here -> https://github.com/orgs/BlueprintFramework/discussions/134
Still facing issues?
Make a thread in #forum or GitHub Discussions. We're happy to help.
More information about the vulnerability is set to release at a later date. Patching or updating your panel is highly recommended. Thanks for using Blueprint <3.
Beta Was this translation helpful? Give feedback.
All reactions