Search

Search:
-::DESCRIPTION
-::DATE

XSS on Google Groups | Video Demo by Ashish Pathak

Good Evening Readers,
Today we gonna post Video Demonstration of Cross Site Scripting on Google Groups.

This video is submitted to us by a security researcher, Ashish Pathak.


For any query regarding this Video, Feel free to contact us..


Hacking Ola Wallet | Writeup by Shubham Paramhans







Recently a security researcher from India, Shubham Paramhans, has found a major bug in Ola that can allow anyone to recharge their Ola Wallet of any amount. You can read the original article from Shubham Here

Submitting this bug to Pentesting-Lab, Shubham Paramhans, added

I booked a cab for my weekend project and I was monitoring my phone traffic from a proxy server. While doing that I saw Ola API calls going from my phone.

After seeing those flashing binaries data going from my system I forgot my weekend project and started tweaking and reverse engineering Ola API’s which eventually resulted in breaking their money transaction system and I was able to recharge my Ola wallet with any amount.


Chapter 0 : Something is not right
I was working on a small side project in which I was monitoring my phone traffic. For this purpose I used MITM Proxy, which is a very light console based proxy server. As I was booking my cab I saw Ola API calls. The structuring of the API calls attracted my attention. Something was amiss here. These calls were simple HTTP requests without any OAuth token mechanism or any other encryption to guard APIs. One can easily replicate these calls from a console or by using Chrome. There are some other clients one can use like PostMan or Advance Rest Client.



Above is a log of request to fetch cabs for a given latitude and longitude. This is exactly what went from my phone to their servers with a few payloads like device-id and install-id. On refining, though, I found most of the things present here were not even required. This goes to show the absence of server-side validation for API calls. Below is what you get in response, a json of cabs near your current location



Chapter 1: Digging the tunnel
After successfully tracking and fetching cabs I was very happy because (no offence to ola) their app sucks, as in really really bad. First of all it crashes a lot. Secondly, I don’t like the UX. I think better things can be done. Just take the example of Uber. Their app works so smoothly and booking a cab is a piece of cake. Thirdly it is very difficult to book a cab. It’s a blink and you miss situation where in microseconds a cab vanishes.

This got me thinking and I created a one tap app where once I’ve set my preferences, a thread can run in the background and ensure a one-tap cab booking. For one thing, it made my life easier while accomplishing the task of fully automating the booking process. A few people might find this offensive but this is the fun in weekend projects; creating small utilities so that you can get even more lazy :p

Then I went greedy (lazier). I thought what if I can book a cab for free?!! That will be one mighty bad-ass thing to do. So I started to trace the recharge API calls.

I did one simple recharge on my phone to get an idea of what was going on. Long story short, one recharge process in three simple
steps.

Step One : Generate an order id which will be used for reference in future,

Step Two : Make a few payment gateway calls to complete the transaction

Step Three : One more API call to Ola’s server to acknowledge the transaction, to complete the process.

After completing the transaction I started connecting the dots to understand their system. Believe me it was one hell of a easy maths. Simply put, it was a very bad design because all the transaction APIs implemented by Ola were using simple HTTP protocol and sending data in plain white text. This was next ‘woohoo’ moment, because this motivated me to find more loopholes and believe me Ola’s system has a lot of them.

Chapter 2: Fire in the hole
After watching, tracing and connecting all the API calls, my console was ready to fire the bomb. Even if I not get to book cab for free but still I can create one app which can book a cab for me in just one single click. To be honest, I was kind of nervous. Let’s accept it, it was easier than I’d ever imagined and if this went right, well you can understand.

Since college days I’ve been making such things. Partly because I enjoyed the thrill of the process more than the end result. It wasn’t exactly like “The Social Network” but something similar.

Coming back to the topic, I had my arsenal ready for attack. With a prayer on my lips, I fired my first shot i.e. generating an order id. It went perfect. I took aim again and below is what a cleaned request looks like, with response from their server.



Now I have one order id that is ready for transaction, which I can use to acknowledge completion. Lock and load!



In few seconds I received a message on my phone, confirming the recharge and I was like YESSSSSS……..its done!!! I just cannot express what it was like. I just fooled one of the biggest startups with millions in funding.

Hearing me shout in excitement, my sleeping flatmate DAERTY came running to the scene, “kya hua be kyu itna chilla raha h, chain se sone bhi nahi deta” (why are you shouting, you never let me sleep peacefully). I said dude watch this. I sent the last request again, pressed enter which culminated with my phone message tone ringing.

Note that I didn’t even generate a new order, it was the same order id. If you still didn’t get the joke — it means that they were not even checking for order id, which simply means you can use the same order id to do as many recharges with whatever amount you want, obviously not like 100's so they get alerted (from what I’m seeing we can safely assume they are not going to). It was hilariously traumatizing (lol).

To summarize this, I think the problem really was in their architecture. I mean for the love of God, you should make order id unique, isn’t it? Ola was not even tracking order ids. Maybe money is getting to their heads. Maybe in the process of putting more taxis on the road they lost track of their technology. Maybe that is why their customer support always sucks. And maybe that’s why they forgot something as basic as this when it comes to library management. Maybe that’s why the Startup of the Year has such a huge security vulnerability.



Below is another screenshot of my android phone showing the successful transactions.



Final chapter:
The Aftermath I was brought up a law-abiding citizen. Ethics are embedded (so I hack ethically). So me and my friend decided to write a mail to Ola to tell/caution them. We definitely did not have any intention of getting them in trouble, even if they seem to have trouble providing customer service.

Where better to shake them out of their slumber than ask their dreadful customer support (that’s right, we are gentle folks). So we wrote them a mail asking in essence — do you guys have any bug bounty program?”. If you’re enough of a techie, you will know how Google deals with bugs. What we got in response was a very ugly and rude response from their them. In retrospect I’m surprised that I was surprised…

Even after such a hurtful response from them, we replied them back saying that it’s fine if they aren’t interested in improving their system. Two days later, we received a mail from their customer support HEAD saying we will get back to you on this (maybe they weren’t that bad). Now what, now we wait…..

1,2,3….7 days i.e. one week was over and there was no response, maybe they were busy talking to cabbies. At that time I was working with Kuliza Technologies, Bangalore. I talked to my senior management people and told them about this. They were very supportive and professional about this episode. They helped me report this issue to the management of Ola and even sent a mail to the CEO with all the details and findings of that hack (not boasting but it was a hack)

A few days later, one of their security people replied. It went something like this

Thanks for reporting this issue to us, we will fix this and will keep you updated.


In short the issues with Ola are :-

1. Weak design of DB and architecture, and glaringly poor implementation on app.For example order-id is supposed to be unique but you can use same order-id to recharge your wallet again and again.

2. It seems that checksum, card id etc isn’t crosschecked with MobiKwik. You can use any gibberish values in place of checksum & card-id, and the recharge will still be done successfully.

3. Lack of implementation of security protocols like HTTPS or any token validation. While making money transactions, some token validation mechanism should have been implemented. At least proper server side validations should be present.


P.S. : Since they haven’t responded well and this issue has been fixed in current version.

Bug on Megneto can restrict User to Login to Account | Writeup by Vishwa Raj

Hello friends, Today we gonna post POC of a bug on Megneto which allows User to restrict to login to their accounts.

This bug has been submitted to Pentesting Lab by Viswa Raj.

Issue :
In this when a user request for a password reset then a unique password is being sended to the user’s gmail and the application won’t allow the user to login until the password at the mail is not being given because application is resetting he password automatically without asking the user permissions

Impact :
Attacker can abuse this functionality easily by requesting a password reset and restrict the user to login his own account for hour’s until user don’t know that the password is at their mail .

Explained Further :
So the attacker will create an easy script in python
to launch a password reset request on the behalf of user’s just via email [Since magento is also vulnerable to user enumeration bug in which i was able to extract the existing user’s into the magento due to improper rate limiting ] so attacker will be giving problem’s to your existing customers and if the same code is used in enterprise magento then it will effect it too .

PS : This bug has been already reported to megneto and unfortunately the denied this bug.

You can see the reply from them..



Video POC :

XSS on Orkut | Video Demo by Tanuj Jane




Recently, Tanuj Jane has submitted to Pentesting-Lab, POC of his one of the Bug Finding that was XSS on Orkut.

We all know about Orkut and Google has stopped this service a long back ago.

Tanuj has submitted video demonstation to us. So check this out guys..


Vishwa Raj | Introduction

Vishwa Raj is one of the best Independent Security Researcher from India. He has been affiliated with Pentesting-Lab to share his Bug Findings and Hall Of Fame.

So far He has been listed in so may Hall of Fame like Facebook bounty ( multiple time ), Apple, Samsung, Hackerank, Hackerearth and also got aknowledgement from Eset and Trend micro.
We will reveal his Findings with proper POC soon on this site..

Stay Tuned with us....

Facebook - Linkshim Evasion and URL Redirection : Write Up by Paul OS




One of the Good Facebook Bug Hunter, Paul OS, has submitted URL Redirection Bug of Facebook to Pentesting-Lab.

Lets Check out the write up by his own words.

Web applications frequently redirect and forward users to other pages and websites, and use untrusted data to determine the destination pages. Without proper validation, attackers can redirect victims to phishing or malware sites, or use forwards to access unauthorized pages.

Recently I was browsing through Facebook mobile (m.facebook.com) and I found a notification that a friend tagged me into a post… well the post wasn’t that interesting so I decided to hide it. When clicking on hide I notice the URL parameter contained a parameter called ‘continue’ followed by stories.php

https://m.facebook.com/feed_menu/?story_fbid=808015282566492&id=100000740832129&confirm=h&continue=stories.php&perm&no_fw=1&_rdr

So I figured that can lead to a URL redirection if I changed the continue parameter to something like http://evilzone.org but the Linkshim was rechecking and returning it back to m.facebook.com/http://evilzone.org but the redirection wasn’t successful but then I noticed that parameter can be tricked using path transversal tricks like ../

When I gave the url parameter something like
&continue=../http://evilzone.org
I was able to bypass the Linkshim and get a successful redirection to Evilzone.org (which by the way is a blocked link by Facebook).

So the full parameter for redirection including the Linkshim evasion was

https://m.facebook.com/feed_menu/?story_fbid=808015282566492&id=100000740832129&confirm=h&continue=../http://evilzone.org&perm&no_fw=1&_rdr

And none of the other parameters needs to be accurate;
the story_fbid and id parameters can be any number so we don’t need victim’s special parameters to execute redirection.

Now the issue have been fixed and Facebook has promised to reward me with 1000$USD for this bug. I would like to thank the Facebook Security Team so much for their cool support and generous amount.

XSS on Intel Website || INTEL



Hi Guyss..
Its my 1st article after a long time...One day,I was downloading drivers from Intel Website(http://downloadcenter.intel.com), Then i saw that on searching for some page which is not present its redirecting to 
https://downloadcenter.intel.com/error.aspx?aspxerrorpath=
Then I tried to XSS that...by using a Payload:
%22%3E%3Cimg%20src=x%20onerror=prompt%281%29%3E
And Bhoommm, XSS!!!  :D :v
https://downloadcenter.intel.com/error.aspx?aspxerrorpath=%22%3E%3Cimg%20src=x%20onerror=prompt%281%29%3E




You can see POC:




Bug Bounty Website List


Product & Services (No Reward)


Product & Services (Hall Of Fame Only)



Reward Program
(To submit you need to sign up to the free
Developer API program)



Source : Bugcrowd

Pentesting | From Where to Start

Many of you have ever wondered from where to start Pen Testing. If yes then you probably tried to get the answer from Google. But frankly speaking, If you are going to search this randomly, Perhaps you will get thousands of results regarding this.

And what you will get? NOthing. They claim to start with XSS, CSRF, SQLi and other types but remeber this all is without even knowing the basics.

Pentesters, newly come in this field, often start with XSS and try to hunt the Big Firms like Facebook, Google with their basic XSS payloads expecting success. But do you know these all big firms havethousands of clever people to review their codes. You have to be more smarter than them to manage to evade filters and by learning payloads you cannot do that.

According to some security researchers, one should learn first the basics of the attack. For Example if you want to learn XSS then you should know What is XSS? How To Expolit XSS? What is the Security Risks to any organization if they are vulnerable to XSS.

Then one should go for XSS payloads and learn how they work. Rather than hunting Big Firms, Try to hunt small scale sites first.

I also give you an advice to visit Blogs of well known Bug Hunters to understand the Flow.

I hope you are cleared with this all. Have a Happy Pentesting. :)

XSS on 000webhost

Good Afternoon Friends,

Today We have a Video Tutorial of XSS vulnerability on www.000webhost.com for you all..

For any query regarding this Video, Feel free to contact us..


Lalit Kumar || Introduction



# About.sh
Lalit Kumar is an under graduate student of Electrical Engineering @Indian Institute of Technology,Bhubaneswar(IIT-BBS). He is an Blogger,Hacker,Graphic Designer,Android Developer,Web Designer and much more... :P :D Now lets come to the point...He is also an IT-Security researcher,  presently working in the field of penetration testing and vulnerability assessments..his field of interest is Vulnerability Assessment, Penetration Testing , Security Auditing/Training, web development, server mangement..etc..

# Experience.sh
He has been working in field of web application security, has helped many giants companies to secure their web app like Mediafire(Link 1,Link2),Got rewards from Intel for reporting Vulnerability in there Website,Got mentioned in Oracle CPU Fix October 2014 (Link1 and Link2)he has been rewarded by many companies like Blackberry,Ebay Inc.,Intel,Barracudalabs,Concrete 5,Microweber,Intuit,etc.
He has been affiliated with Pentesting-Lab to share his Bug Findings and Hall Of Fame.

Tanuj Jane - Introduction

Tanuj Jane is an Independent Security Researcher from India. He has been affiliated with Pentesting-Lab to share his Bug Findings and Hall Of Fame.

He has found some critical vulnerability on..... and so far he has got some positive replies too.

We will reveal his Findings with proper POC soon on this site..

Rizwan Shaikh - Introduction

Rizwan Sheikh is an Independent Security Researcher from India. He has been affiliated with Pentesting-Lab to share his Bug Findings and Hall Of Fame. He has got so many Hall of Fame since now. We will reveal his Findings with proper POC soon on this site..

Paul OS - Introduction

Paul OS is an Independent Security Researcher. He has been affiliated with Pentesting-Lab to share his Bug Findings and Hall Of Fame.

He has got so many Hall of Fame since now but according to him, Listing on Facebook White Hat page is Fabulous remark from his side. We will reveal his Findings with proper POC soon on this site..

Ashish |Pathak - Introduction

Ashish Pathak is an Independent Security Researcher from India. He has been affiliated with Pentesting-Lab to share his Bug Findings and Hall Of Fame.

He has found some critical vulnerability on Blogger, Google, Facebook, Yahoo, Sony etc. Some has been revealed and others are waiting for suitable reply.

We will reveal his Findings with proper POC soon on this site..

Powered by Blogger.

Popular Posts