Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Becoming the Hacker

You're reading from   Becoming the Hacker The Playbook for Getting Inside the Mind of the Attacker

Arrow left icon
Product type Paperback
Published in Jan 2019
Publisher Packt
ISBN-13 9781788627962
Length 404 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Adrian Pruteanu Adrian Pruteanu
Author Profile Icon Adrian Pruteanu
Adrian Pruteanu
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Introduction to Attacking Web Applications FREE CHAPTER 2. Efficient Discovery 3. Low-Hanging Fruit 4. Advanced Brute-forcing 5. File Inclusion Attacks 6. Out-of-Band Exploitation 7. Automated Testing 8. Bad Serialization 9. Practical Client-Side Attacks 10. Practical Server-Side Attacks 11. Attacking APIs 12. Attacking CMS 13. Breaking Containers Other Books You May Enjoy
Leave a review - let other readers know what you think
Index

Situational awareness

Now that we have access to the shell of the Docker container, we should look around and see what else we can find. As we've mentioned before, Docker containers are not VMs. They contain just enough binaries for the application to function.

Since we have shell access on the container, we are constrained to the environment it provides. If the application doesn't rely on ifconfig, for example, it will likely not be packaged with the container and therefore would be unavailable to us now.

We can confirm that our environment is somewhat limited by calling:

weevely> ifconfig
sh: 1: ifconfig: not found
weevely> wget
sh: 1: wget: not found
weevely> nmap
sh: 1: nmap: not found

We do, however, have access to curl, which we can use in place of wget:

weevely> curl
curl: try 'curl --help' or 'curl --manual' for more information

In the worst-case scenario, we could also upload the binaries through Weevely's :file_upload command...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime