My Intro to CIS class uses "Cengage" for programming sandboxes and whatnot.

Whoops.

What am I looking at here

@AlgoRythm the sandbox's terminal, which is literally root bash

@Parzi what's wrong with that?

@groxx @AlgoRythm Other people can see files I make. It's not a sandbox.

@groxx can i choose both?

also "ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash" is rather interesting...

@Parzi Oh, these are important details!

for i in range (1, 1000000):

file = open(f"penis{i}.txt", "a+")

print("Penis", file=file)

file.close()

So? Getting a root terminal is normal, as those machines are virtual machines and reset if misused.

@groxx running in containers as root is actually discouraged practice, because every user that has jumped out of a container into the OS has been root inside.

@sbiewald my main concern is someone bankrupting them with the infinite bandwidth. (Also, confirmed: Amazon server!)

also what can be done with ```/etc/cloud/cloud.cfg```? Looks like some cloud config, but why would it be in every machine?

@Parzi get the container's IP, and see if you can figure out their internal network from there.

Look for the docker socket if you want to escape.

@arcsector Just because you're root inside a container, does not mean the container runs privileged.

Have fun exploiting!

Oh, almost forgot!
I found a pretty awesome DEFCON talk about docker container escapes. You may want to take a look. :)

https://youtu.be/1FB58EVWAOU

@sbiewald maybe i wasnt clear: you shouldnt do either. You shouldnt be running a container with root and you shouldnt be root inside the container.

@arcsector @sbiewald ESPECIALLY not just for a Python sandbox.

@PrivateGER @AlgoRythm it's an Amazon EC2 instance, according to configs and things.