# BM01

## **About The Challenge** <a href="#about-the-challenge" id="about-the-challenge"></a>

| Type   | Difficulty |
| ------ | ---------- |
| Binary | Medium     |

## ‌Solution

The second binary challenge was also a Linux binary, but here it was not easy.&#x20;

![](/files/-MO7hIeMhql-KV1_8ojq)

By executing the binary program, we prompting with the message *Can you get the flag out of me?.*&#x20;

In this challenge we have the debug the binary in order to solve it. We can use any debugger tools, I used IDA. &#x20;

![](/files/-MO7i4esLM2i8eOaXDvi)

Using IDA I run the program to debug it. As previous figure shows on the left windows the functions that the program having, I make break point the end before the program stops and exit. To investigate the heap data and what is stored on the program memory.&#x20;

![](/files/-MO7ji-ijKs7az8iiQa3)

As above figure shows at the button section is heap data.&#x20;

![](/files/-MO7k9txV_lhLlLCiucO)

I found the flag that is written in tiny letters.&#x20;

![](/files/-MO7kbm4BEdRTLc4Mz0e)

After that, I used CyberChef in order to decode Hex values and get the actual letters.&#x20;

**Flag:** ⁿᵒᵗᴳᵒⁱⁿᵍᵀᵒᴹᴬᴷᴱᵗʰⁱˢᴼⁿᵉᔆ⁰ᴱᶻ


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://kf0k-blog.gitbook.io/ctf/writups/sans/binary/bm01.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.