Root Password Not Working & CTF Scenario Errors when Attempting to Create One.

[cliffe]

Root Password Not Working & CTF Scenario Errors when Attempting to Create One.

[thomashaw]

Hi @kanoble88,

If you comment out the following block in the scenario.xml file you're using, SecGen will not change the default password on the VM.

<build type="cleanup">
      <input into="root_password">
        <generator type="strong_password_generator"/>
      </input>
</build>

I have reverted a recent commit which broke the basic_narrative.xml scenario, if you update your branch it should generate now.

Thanks for the info and have fun!

[kanoble88]

Awesome thanks! This program is fantastic for those of us new to CTF events and putting them together.

[kanoble88]

Is it supposed to create 3 VMs at a time? When I look at my virtualbox after it says the VMs were created I have one for the decode me, one for into the wild and another for that escalated quickly.

[thomashaw]

Yes the flawed_fortress.xml scenario will generate 3 VMs. You can see how many VMs each scenario will create by looking at the number of <system> tags in the scenario xml file.

The reason we have multiple VMs is because one box has a privilege escalation to root vulnerability. If that vulnerability is exploited successfully a bunch of the flags would be accessible without solving the other challenges.

[kanoble88]

Ohh I get it now. Is is possible to export the flags for a VM to a CTF program like the Facebook CTF? I have been using that lately and was debating on copying the information from the XML to the facebook CTF using their json template.

[cliffe]

Hi @kanoble88
It would be great if when outputting the project, SecGen also output the files in Facebook CTF format (and other front ends, such as CTFd).
Currently we have been focussing on our own CTF frontend.

We currently have multiple hints per flag, and even shared hints among flags where the flag requires multiple shared steps. We support this in our front end, where submitting a flag will unlock any shared hints (for example, two flags encoded different ways behind the same software vulnerability, share hints regarding the vulnerability). Also because of the nature of having a VM, means that you might find a flag, without knowing what challenge the flag was from.

Not sure how compatible all that is with Facebook CTF, but the hints could be removed or simplified, and hopefully there is a way of making a single flag submission. Feel free to investigate and report back :)

Cheers.