Skip to main content

Create a Docker Container in the Host network

 

#Start a new container - which has the same ip as Host Container
docker run -it --network host kalilinux/kali-rolling

#Start a container 
docker start Container_ID

#Attach a container 
docker attach Container_ID
ctrl+p & ctrl+q to detach from a container without killing it 

#Start a container in Detached mode
docker run -d --network host kalilinux/kali-rolling

#Start a container in bridge network 
#Default is bridge network
docker run -dit --name test kalilinux/kali-rolling /bin/bash

Bridge network = new Docker network - separate network
Host = Docker Host network 

#Create a bridge network
docker network create --driver=bridge my_bridge_network --subnet=10.10.10.0/24 --gateway=10.10.10.1

#Run the container in Bridge network 
docker run -it --name my_container --network my_bridge_network --ip 10.10.10.2 ubuntu:latest
Moving Docker Container to a Different Host 

#list the containers and copy the id
docker container ls 

#stop the container
docker stop <Container_ID_or_name>

#Create a new image 
docker commit <container_ID> <new_name:tag>

#save the image to a tar file to export
docker save -o <container_backup.tar> <Image_name>

#Push the container to a new Host
scp <container_backup.tar> root@10.10.10.10:/home/backup/

#Login to the new host and load the container, might take some time based on the container size
docker load -i <container_backup.tar>

#List the images, confirm your new docker container here 
docker images

#Create/run the container 
docker create --name kali container_backup
docker container container_id start
or
#create and start the container docker run -it --name kali --hostname kali <Image_id> #Setup auto restart docker update --restart unless-stopped kali #Verify restart status docker inspect -f '{{.HostConfig.RestartPolicy.Name}}' kali #make sure docker starts on boot sudo systemctl enable docker
Basic Docker Commands

#list containers
sudo docker ps 

#Get a shell 
docker exec -it <container_name_or_id> /bin/bash



Comments

Popular posts from this blog

POC Links for CVE's

  Serach for a CVE here first - Trickest/cve Apache CVE-2024-38475 - CVE-2024-38475 #version less than 2.4.51 CVE-2021-44790 - h ttps://www.exploit-db.com/exploits/51193 #Apache HTTP Server 2.4.50 CVE-2021-42013 - https://www.exploit-db.com/exploits/50406 use https://github.com/mrmtwoj/apache-vulnerability-testing for below CVE's CVE-2024-38472: Apache HTTP Server on Windows UNC SSRF CVE-2024-39573: mod_rewrite proxy handler substitution CVE-2024-38477: Crash resulting in Denial of Service in mod_proxy CVE-2024-38476: Exploitable backend application output causing internal redirects CVE-2024-38475: mod_rewrite weakness with filesystem path matching CVE-2024-38474: Weakness with encoded question marks in backreferences CVE-2024-38473: mod_proxy proxy encoding problem CVE-2023-38709: HTTP response splitting EXIM #suppodily should work for versions below Exim 4.96.1 - is not accurate CVE-2023-42115 - https://github.com/AdaHop-Cyber-Security/Pocy/tree/main

Hash Extension Attacks

  #Install Dependencies sudo apt-get install libssl-dev #Download Hash Extender git clone https://github.com/iagox86/hash_extender.git cd hash_extender make #Run it /hash_extender --data 'username=admin' --secret 16 --append '&isLoggedIn=True' --signature d3a85d3b3087c7e841f84eb4316765c6e1f786074a1f1db996b2e0f8c96f197e2f55433920a630feb07daafadefbc13c947e5225fc509f8241f57f47a8df5311 --format sha512