Self Notes: Web Security Academy File upload vulnerabilities Lab 6

-


(In the name of Allah, the most gracious, the most merciful)    بِسْمِ اللَّهِ الرَّحْمَنِ الرَّحِيم

This Lab as with the previous labs is quite easy, the difficulty is practitioner-level, so I will make it very brief as most of the concepts are the same. In fact, the only reason I am writing about it is that it has one uncommon feature (EXIF, at least to most people) otherwise it's pretty straightforward and easy.

Task: This lab contains a vulnerable image upload function. Although it checks the contents of the file to verify that it is a genuine image, it is still possible to upload and execute server-side code.

To solve the lab, upload a basic PHP web shell, then use it to exfiltrate the contents of the file /home/carlos/secret. Submit this secret using the button provided in the lab banner.

You can log in to your own account using the following credentials: wiener:peter

From the task statement, we understand that the content of the file is actually checked to verify whether it's an image or not, this is usually a good practice, but it has its own caveats. If the file extension is not validated and we can add meta-data to the file we are uploading, we can create a polyglot file which is both an image and a PHP file at the same time, and then upload it with a .PHP extension, to exploit the system. That's exactly what we are going to do in this lab.

We are going to use ExifTool to add meta-data to the image file.



We've embedded a PHP script in the comment meta-data section of the image and we can verify that by opening the image in ExifTool:


Now, all we have to do is rename the file and upload it to the lab server.

Then we try accessing the file:


We obtain the following response:


And we've found Carlos' secret. We submit it and solve the lab.


And that completes it for this Lab. Just one more to go, see you in the next post.

For some nifty polyglot tricks, check out Ange Albertini's work in PoC||GTFO 0x19.


Comments

Post a Comment

Popular posts from this blog

Before You Dive In...

-
I have always wanted to write, partly to improve my writing skills but also to document my research in reverse code engineering, software exploitation and computer programming in general, my current goal is to have at least a post a week, but since am just starting out I do not know how feasible that will be considering school and my need for quality over quantity. In the coming weeks, I will post on varying topics from software reverse engineering to exploitation and basically anything that interest me. My primary aim is just to cement my knowledge in my fields of interest by giving back to the community as I learn and hopefully along the way help someone trying to learn. A quick disclaimer though is that I am no professional at either writing or the subject on which I will be writing (at least for now),  am just trying to navigate through the vast ocean of knowledge hoping to pick one or two things along the way, so corrections, constructive criticism, and even unconstructive ones
Read more

OverTheWire: Bandit Lab

-
Image
Bismillahirrahmanirrahim (In the name of Allah the most gracious, the most merciful) So recently I and @electro decided to solve wargames and CTFs in the spirit of honing the skills and because we are preparing for something really important (another post for another day). We decided to start with the labs at overthewire  and the first on the list was Bandit Lab. Bandit Lab was a fun experience, mostly easy, except for one or two tricky levels, level 26 and level 33 in particular. This Labs weren't so difficult but required a bit of thinking outside the box, hence why am documenting them. NB : this writeup doesn't include our thought process while solving the levels Level 26 Level Description When we attempt to login to this level using the private key obtained from the previous level we get automatically logged out and since the level goal already informed us that we are dealing with a different shell, we need to figure out what it is and how to break out of it. Above is the
Read more

SSRF Notes: PortSwigger Labs Continued

-
Image
  Lab 3: SSRF with blacklist-based input filter Task :  This lab has a stock check feature which fetches data from an internal system.  To solve the lab, change the stock check URL to access the admin interface at http://localhost/admin and delete the user carlos.  The developer has deployed two weak anti-SSRF defenses that you will need to bypass. This Lab is just like the previous ones except that we need to bypass blacklist filters. This is what a normal request to the stock check feature looks like: Passing http://localhost/admin to the stockApi parameter does not work this time. we get this response: That's the filter blocking us. It turned out 127.0.0.1, localhost, admin are all blacklisted so cannot be used. So after trying a couple things the following was able to bypass the filter: We get the following response: So to complete the Lab we just proceed to delete carlos. And that's it Lab solved.
Read more