PII data exfiltration within minutes

Mayank Garg
4 min readDec 12, 2022

--

Hello Everyone,

Here I am with a story of one of my findings where I was able to exfiltrate complete PII data and not just of their customers but also their employee’s PII data.

So, the company is about crypto exchange and is a popular company in the US. As the bug is not fixed yet let us make an alias for the domain name and call it crypto.com.

On the first day of hacking on this I started with reconnaissance, obviously. Got the subdomains, fuzzed for different endpoints, port scanning, and other stuff. The most exciting thing was their main application only. So I started on that main application which is a crypto exchange platform. I found a couple of low-hanging bugs but I wanted to find a bug with high severity.

I again started the next day and the first thing I did was GitHub recon.

Do you know what GitHub recon is?
If you don’t, I’ll tell you in simple words. It is simply doing reconnaissance on GitHub.
Still not clear? So, the companies develop a product and what goes into developing a product? Programming codes. And that is developed by a team of software developers. GitHub provides a platform where software developers can come and develop something together, share codes, and collaborate.

How can you use GitHub to find something useful?
So, during developing a product and programming and collaborating on GitHub the developers often share something confidential which can be a password to a live login page or even to an SSH server, tokens, API keys, and other sensitive information.
You can make queries and search on GitHub to fetch sensitive information. Examples:
crypto.com token
crypto.com password
crypto.com “Authorization: Bearer”
et cetera

What I did?
I formed a query as “crypto.com token” and I found a repository with a JWT in a code. That JWT had admin privileges.

But how I knew that the token had admin privileges? You can use https://jwt.io/ to get more information about the structure of the JWT. Like you can get the signing algorithm used, the body of the JWT (actual data of JWT), etc. There was a key-pair in the body of the JWT as “authority”: “ADMIN”. I will surely write a blog explaining JWT in detail and some common attacks you can make use of if you find any JWT during your penetration test or bug hunt.

NOTE: You should verify every sensitive information found as they can be dummy tokens/passwords or there are chances that they had already been nullified by the company.

Then I started looking for endpoints that were meant for admin users and needed some kind of Authorization. I found 3 such endpoints.
Next thing was to send the JWT to these endpoints and I did this by adding a header in the HTTP Request: Authorization: Bearer <JWT_Token>
To my surprise the JWT Token was valid and I got a response with massive data.
You can also make a request with cURL: curl -X GET ‘https://api.crypto.com/transaction/admin/orders/list' -H “Authorization: Bearer <JWT_Token>”

What kind of information was fetched?
First endpoint:
It contained PII data of the employees like their email addresses and phone numbers.
Second endpoint: It contained PII data of customers like their email addresses and phone numbers, whether their KYC is done, etc.
Third endpoint: It contained the transaction details like what cryptocurrency they bought, at what rate, transaction ID, etc. This data was massive and this used to get refreshed after some time as the transactions used to take place at an extremely high rate.

This took me around 15–20 minutes on the second day to exfiltrate this much of data.

What did I get as a reward?
After 3–4 days of reporting, I got a reply that the company has closed their bug bounty program, hence, they won’t be able to pay me. That was disheartening and also that is not fair.
But they offered me a job role as a Security Engineer. I was delighted about that but I had an internship at Deloitte USI lined up for the very next month. So, I declined that offer and went for an internship at Deloitte.
I’ll write a blog on that as well sharing my experience working at Deloitte and also how I got an internship at Deloitte.

Till then, take care ✌️, and keep hustling 💪

--

--

Mayank Garg
Mayank Garg

Written by Mayank Garg

Penetration Tester | Application Security | Bug Hunter | CEH v11 (Master)

No responses yet