# Creating Python exploit

In the home page there was mention to feeed.py –

<figure><img src="/files/2iSIUR46kESB3oX1JbVR" alt=""><figcaption></figcaption></figure>

I did not see this in the results of filepath I got back from the respose I got back from Burpsuite but I can still call on the file to see what I get

<figure><img src="/files/dGlAHwgohmh9R6UGniLs" alt=""><figcaption><p>results of feed.py</p></figcaption></figure>

In the subject I still cannot get the full path to the file maybe because of XML bad characters.

Python web applications usually create routes, then give the routes a page that then define the code as per lines 15, 19 and 23

\
Now, i need to create a script to exploit pickle.

<figure><img src="/files/z3uPLufr3cJZySUu5uGy" alt=""><figcaption><p>Can see here they use urlsafe b64decode, so in the script I will include b64encode</p></figcaption></figure>

The script -&#x20;

<figure><img src="/files/IrTNiN35DSm4ePqOPEmx" alt=""><figcaption></figcaption></figure>

Imported base64 as necessary

Line 4 is from pentest monkey\_chichi - <https://pentestmonkey.net/cheat-sheet/shells/reverse-shell-cheat-sheet> -NC

"pickkle.dumps" is in regards to pickleloads from the original feed.py file.

<figure><img src="/files/bpVIvbm9gAvLUEAgOGoQ" alt=""><figcaption></figcaption></figure>

First attempt error.syntax. I will change it so that I need to write the whole b64encode

(To be continued)


---

# 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://oklencodes.gitbook.io/untitled/ctfs/devoops-ctf/creating-python-exploit.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.
