Luminate Store Basics defacement and potential takeover

Aug 30, 2017 · 3 min read

This vulnerability was found when testing the Stores Basic service of Luminate. In this service, we can create a store from where we can sell our products. Luminate service provides a whole CMS for this activity. Here is the snapshot of the backend of the CMS:

Image for post
Image for post
Store Basics’ Dashboard

I first ran some CSRF test in the Settings section of this app. In the settings, user can add business information that will be used by Luminate to contact the admin. Along with that, they can also upload Logo and add title for the website. My initial test gave me a successful CSRF attack. I will explain each step below because the generation of attack was complex at first.

Update: this blog covers two main bugs together: 1) CSRF In Luminate allowing to update business information 2) Session issue in Luminate allowing you to modify another user’s data remotely. One has higher impact than the other.

Getting the CSRF

When a business information is modified, a POST request is made to:

In the POST request JSON request like this is passed:

ysbparams parameter in the url specifically stood out during the testing because it had ==in the end. We went with the idea that this could be a base64 and it was indeed a base64. Once decoded, we got something like this: (this is edited to hide information)

Once that was decoded, I had to identify ways to get the bizid parameter. I noticed that this could easily be grabbed from the source code of the store url. So I could change that and encode the JSON then edit the url with new ysbparam. Initially, when testing this CSRF it did not work, because the server only accepted Content-Type: application/json. So in the end, I used AJAX to send a request with the type set as application/json.

CSRF -> Takeover

After I had the CSRF, I decided to dig deeper and noticed that in the POST request there was a certain cookie called ysbauth. This cookie was also base64 encoded. Following is an example of base64 encoded ysbauth.

When we deocde the base64, we get the following JSON:

During testing, I found that if I only change the bizid in the ysbauth to one of our victims, I could successfully modify the file. For this attack, first I change the YSBParam by changing bizid and biz_url (like we did for the CSRF) and change the ysbauth with victim’s bizid. Once that is done you could modify the business information of your victim.

After 1 hr of complete testing, I found that all the modules in Store Basics were vulnerable. We could add our own Google Analytics code to the website which would allow monitoring of the website, we could also view coupons of other sites, add products and conduct many other attacks. This concluded that when ysbauth was manipulated, it basically gave access to another user’s session allowing us to modify their store basics profile.

Special thanks to the Yahoo security team for being extremely responsive and fast in the fix. I recommend all hackers to try Yahoo!’S bug bounty.



Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store