Yelp Deconstruction 2

Yelp uses there own flavor of GraphQL with a UI site generator called CHAOS. GraphQL has Denial Of Service attacks with long queries but Yelp does not reward DOS attacks and requests that bug bounty hunters do not flood the API with them. They use batch queries to the API with cryptic looking large cookies that detail user location by coordinates. The cookies are large with a key-value format. They use data dome against bots so the web application firewall picks up whether there is a proxy being used denying access to the website depending on whether you use the Burp Suite chromium browser. I have only come across loading issues when proxying through fire fox and haven not been denied. Yelp uses cookielaw CDN and also has its own yelp CDN which means there could be vulnerabilities with caching and web cache deception or web cache poisoning the kind of attacks that are hard to produce but I should research further. Because they have their own CDN means it might still be in scope of the bug bounty program? They also use fastly as a CDN but fastly is out of scope being a third party. An API endpoint is https://api.yelp.com/v3 tried fuzzing the API with FFuf but did not get any hits that returned 200. https://api.yelp.com/v3/graphql is the GraphQL API endpoint, I tried different versions but returned nothing in repeater having tried to find an easy win. I tried to simply replace a user id with another user id but it was unfruitful trying again for an easy win. I used a different tab container and a temporary email for signing up a different user to do that but nothing came of it. It is a good way to find IDOR's by signing up different accounts and seeing if you can access other user's account, a form of broken access control. There are multiple different ids like bsi and wdi with their own encoding which is what I tried switching between different users. I was able to get it to work once but it was not evident that it was an exploitable bug. Yelp is partnered with Door Dash for deliveries though there is no payment functionality and you are directed off site to Door Dash. uWSGI is the web server used behind the scenes. They use a python framework called Pyramid. Tried to find a uWSGI cve but there were only old CVE's or did not apply because Apache server has something called uwsgi which is not the same web server as uWSGI. Dug through the Yelp Engineer blog and found their home made template engine called yelp_cheetah https://github.com/Yelp/yelp_cheetah. Would this be vulnerable to a server side template injection (SSTI) like other templating engines? I have a tentative grasp of SSTI's so I do not know. But the source code is on the github.

Comments

Popular posts from this blog