Open
Conversation
added 6 commits
December 23, 2025 18:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addition of a new scenario as requested.
Scenario contains an instance of drupal 8.5.0 running on the web server. This is vulnerable to drupalgeddon2 which grants a shell as www-data. A flag is preleaked in the robots.txt which can be found before exploitation. Another flag can then be found within /var/www/sites/default/settings.php . The scenario also contains a random priv esc vulnerability which then contains the final flag in the /root directory.
The current implementation involves a pre setup version of drupal 8.5.0 to overwrite the /var/www/drupal-8.5.0. It also imports a pre setup sql database. The reason for this is because I could not find a way to configure drupal upon installation without it being through the browser, which couldn't be automated easily.
In the future, the drupal_850 vulnerability could be altered to allow for a randomised front page which could contain credentials or organisation details.