mirror of
				https://github.com/mealie-recipes/mealie.git
				synced 2025-10-31 10:13:32 -04:00 
			
		
		
		
	feat: Create Recipe From HTML or JSON (#4274)
Co-authored-by: Kuchenpirat <24235032+Kuchenpirat@users.noreply.github.com>
This commit is contained in:
		| @@ -18,7 +18,7 @@ Use your best judgement when deciding what to do. | ||||
|  | ||||
| By default, the API is **not** rate limited. This leaves Mealie open to a potential **Denial of Service Attack**. While it's possible to perform a **Denial of Service Attack** on any endpoint, there are a few key endpoints that are more vulnerable than others. | ||||
|  | ||||
| - `/api/recipes/create-url` | ||||
| - `/api/recipes/create/url` | ||||
| - `/api/recipes/{id}/image` | ||||
|  | ||||
| These endpoints are used to scrape data based off a user provided URL. It is possible for a malicious user to issue multiple requests to download an arbitrarily large external file (e.g a Debian ISO) and sufficiently saturate a CPU assigned to the container. While we do implement some protections against this by chunking the response, and using a timeout strategy, it's still possible to overload the CPU if an attacker issues multiple requests concurrently. | ||||
| @@ -33,7 +33,7 @@ If you'd like to mitigate this risk, we suggest that you rate limit the API in g | ||||
|  | ||||
| ## Server Side Request Forgery | ||||
|  | ||||
| - `/api/recipes/create-url` | ||||
| - `/api/recipes/create/url` | ||||
| - `/api/recipes/{id}/image` | ||||
|  | ||||
| Given the nature of these APIs it's possible to perform a **Server Side Request Forgery** attack. This is where a malicious user can issue a request to an internal network resource, and potentially exfiltrate data. We _do_ perform some checks to mitigate access to resources within your network but at the end of the day, users of Mealie are allowed to trigger HTTP requests on **your server**. | ||||
|   | ||||
		Reference in New Issue
	
	Block a user