mirror of
https://github.com/andwati/andwati.com.git
synced 2026-11-20 23:48:49 +00:00
switched theme
This commit is contained in:
+18
-19
@@ -6,14 +6,13 @@ date = 2025-08-03
|
||||
tags = ["ctf", "rev", "web", "forensics"]
|
||||
+++
|
||||
|
||||
|
||||
Over the weekend, I had the opportunity to participate in the mmuctf 2025. It was an individual jeopardy style CTF targeted towards beginners and intermediate people in cybersecurity. This is a write-up to explore some challenges I did, or at least almost did.
|
||||
Over the weekend, I had the opportunity to participate in the mmuctf 2025. It was an individual jeopardy style CTF targeted towards beginners and intermediate people in cybersecurity. This is a write-up to explore some challenges I did, or at least almost did.
|
||||
|
||||
## Welcome
|
||||
|
||||
>Through the shadows of the cave, at the door I had a zeal to get a welcome flag, but I couldn't see it though
|
||||
I could hear it calling for me to get it. Happy hacking
|
||||
{: .prompt-info }
|
||||
> Through the shadows of the cave, at the door I had a zeal to get a welcome flag, but I couldn't see it though
|
||||
> I could hear it calling for me to get it. Happy hacking
|
||||
> {: .prompt-info }
|
||||
|
||||
This was a sanity check flag. I believe competitions pose such challenges that you can't get zero points. It's the same as flags in Discord servers, a flag after completing the feedback form, or just other free points.
|
||||
|
||||
@@ -22,12 +21,12 @@ The challenge description talked about the `door`, my first instinct was to view
|
||||
```zsh
|
||||
┌──(mockingspectre㉿blackout)-[~/ctf/mmuctf2025]
|
||||
└─$ echo -n "bW11Y3Rme3dlbGNvbWVfZmxhZ19hZGlvc19NdWNoQGNob30=" | base64 -d
|
||||
mmuctf{welcome_flag_adios_Much@cho}
|
||||
mmuctf{welcome_flag_adios_Much@cho}
|
||||
```
|
||||
|
||||
## My First App
|
||||
|
||||
>Our intern dev swears this app’s secure...
|
||||
> Our intern dev swears this app’s secure...
|
||||
|
||||
This was a web challenge with an account creation form. Let's fire up Burp. The account creation request didn't seem suspicious for now, so I sent it to the repeater to abuse it some more. The response seemed interesting, the user id was in the query parameter: `GET /profile.php?id=5 HTTP/1.1`. This was a nice candidate for an Insecure Direct Object Reference(IDOR). I tried repeating the request with values from 0-4. The flag was at 1, the admin user's account.
|
||||
|
||||
@@ -37,7 +36,7 @@ mmuctf{1d0r_4dm1n_4cc3ss_1s_c0mpr0m1s3d}
|
||||
|
||||
## Ledilect
|
||||
|
||||
>Sometimes the path you take is just a jump away.
|
||||
> Sometimes the path you take is just a jump away.
|
||||
|
||||
This was a simple one, I knew what the challenge wanted, but I couldn't get myself to exploit it, definitely a skill issue. The webapp had a landing page that had a button that made this request:
|
||||
|
||||
@@ -59,9 +58,9 @@ Looking at that, I suspected an open redirect vulnerability, but I don't know an
|
||||
|
||||
## Meet my X
|
||||
|
||||
>In the�days оf cοmfort i met this girl at the Jobless соrner. Аt the�doоrs and windows of iddleness i approached, oops she smiled and thats how i knew she was the one. I guess thatsss whyyy i learned on getting Flags because be warned she later left me at first it feels like a green flag i guess no life was there on blood(heart_break)
|
||||
> In the�days оf cοmfort i met this girl at the Jobless соrner. Аt the�doоrs and windows of iddleness i approached, oops she smiled and thats how i knew she was the one. I guess thatsss whyyy i learned on getting Flags because be warned she later left me at first it feels like a green flag i guess no life was there on blood(heart_break)
|
||||
|
||||
This challenge involved homoglyphs, a character or a sequence of characters that looks very similar or identical to another character or sequence of characters, but has a different meaning, encoding, or origin.
|
||||
This challenge involved homoglyphs, a character or a sequence of characters that looks very similar or identical to another character or sequence of characters, but has a different meaning, encoding, or origin.
|
||||
|
||||
A sentence might look normal, but if you copy it into a text editor that shows Unicode details or a specialized homoglyph detector, you'll see different underlying character codes.
|
||||
|
||||
@@ -73,8 +72,8 @@ mmuctf{oops_twitter_steg_1s_fun}
|
||||
|
||||
## Shadow
|
||||
|
||||
>Look beyond the appearance, perhaps their numerical essence will guide you to the flag.
|
||||
Can you reveal what lurks in the shadow?
|
||||
> Look beyond the appearance, perhaps their numerical essence will guide you to the flag.
|
||||
> Can you reveal what lurks in the shadow?
|
||||
|
||||
This was another stego challenge; there is an image with what looks like a color palette. The description hints at 'numerical essence', so it might be something to deal with the hex values of the colors. I used this site <https://imagecolorpicker.com/> to extract the hex values.
|
||||
|
||||
@@ -99,7 +98,7 @@ mmuctf{4lw4y5_h1dd3n_1n5d3_m3}
|
||||
|
||||
## Revealme
|
||||
|
||||
>We found this mysterious executable on an old USB stick... Can you figure out how to get it to reveal the flag?
|
||||
> We found this mysterious executable on an old USB stick... Can you figure out how to get it to reveal the flag?
|
||||
|
||||
The provided file is an ELF executable binary.
|
||||
|
||||
@@ -173,7 +172,7 @@ mmuctf{r3v3rs1ng_st4rt3r}
|
||||
|
||||
## Flicker
|
||||
|
||||
>An ordinary looking Android app... or is it?
|
||||
> An ordinary looking Android app... or is it?
|
||||
|
||||
The provided app is an Android APK. Let's fire up jadx-gui. The package name is `com.example.blink`. There is an interesting class `r2d2`. In the onCreate method, there is an image string variable that seems to contain base64 image data.
|
||||
|
||||
@@ -190,8 +189,8 @@ CTF{PUCKMAN}
|
||||
|
||||
## Open_Secrets
|
||||
|
||||
>Someone trusted the wrong site and network didn’t forget. Can you piece together what was left behind?
|
||||
Some people still think locks are optional on digital doors.*
|
||||
> Someone trusted the wrong site and network didn’t forget. Can you piece together what was left behind?
|
||||
> Some people still think locks are optional on digital doors.\*
|
||||
|
||||
The provided file was a network capture pcap file. For people who don't know, pcap (a packet capture) consists of an application programming interface (API) for capturing network traffic.The challenge title and filename hint at unencrypted traffic. Open up Wireshark and apply an HTTP filter. There is an HTTP stream that leaks the flag:
|
||||
|
||||
@@ -229,7 +228,7 @@ usb.transfer_type == 0x01
|
||||
usb.transfer_type == 0x01 && usb.dst == "host" && !(usb.capdata == 00:00:00:00:00:00:00:00)
|
||||
```
|
||||
|
||||
Crafting a tshark command to get the leftover capture data for the above filters and redirect it into a file
|
||||
Crafting a tshark command to get the leftover capture data for the above filters and redirect it into a file
|
||||
|
||||
```zsh
|
||||
tshark -r log.pcap -Tfields -Eseparator=, -e thekey.pcapng -Y 'usb.transfer_type == 0x01 && usb.dst == "host" && !(usb.capdata == 00:00:00:00:00:00:00:00)' | sed 's/://g' > usb.capdata
|
||||
@@ -238,9 +237,9 @@ tshark -r log.pcap -Tfields -Eseparator=, -e thekey.pcapng -Y 'usb.transfer_type
|
||||
```zsh
|
||||
┌──(mockingspectre㉿blackout)-[~/ctf/mmuctf2025]
|
||||
└─$ tshark -r thekey.pcapng -Tfields -Eseparator=, -e usb.capdata -Y 'usb.transfer_type == 0x01 && usb.dst == "host" && !(usb.capdata == 00:00:00:00:00:00:00:00)' | sed 's/://g' > usb.capdata
|
||||
|
||||
|
||||
┌──(mockingspectre㉿blackout)-[~/ctf/mmuctf2025]
|
||||
└─$ cat usb.capdata
|
||||
└─$ cat usb.capdata
|
||||
0000190000000000
|
||||
00000c0000000000
|
||||
00000c1000000000
|
||||
|
||||
Reference in New Issue
Block a user