Full Read Server-Side Request Forgery (SSRF)
Discription

# Description
In the recipe edit page, is possible to upload an image directly or via an URL provided by the user. The function that handles the fetching and saving of the image via the URL doesn’t have any URL verification, which allows to fetch internal services.


Furthermore, after the resource is fetch, there is no *MIME type* validation, which would ensure that the resource is indeed an image. After this, because there is no extension in the provided URL, the application will fallback to `jpg`, and `original` for the image name.


Then the result is saved to disk with the `original.jpg` name, that can be retrieved from the following URL: `http:///api/media/recipes//images/original.jpg`. This file will contain the full response of the provided URL.

# Proof of Concept
For testing purposes, I started an internal-only HTTP server, listening at port `8000`, along side the application.


1 – Login and edit an existing recipe.

2 – Click in the `Image` button and insert an URL, in this case will be the target HTTP server: `http://127.0.0.1:8000/`
![2](https://i.imgur.com/CIep9Ox.png)

3 – Visit the `http://localhost:9091/api/media/recipes//images/original.jpg` URL and get the internal HTTP server response.
![3](https://i.imgur.com/ud5TXMD.png)Read More

Back to Main

Subscribe for the latest news:
Generated by Feedzy
%d bloggers like this: