My-Methodologies/recon-strategies-by-other-hackers/js-is-l0ve-..md

description
source: https://sechunter.medium.com/js-is-love-%EF%B8%8F-ca393a4849e9

🔎 JS is l0ve ❤️.

Hello Everyone (Ram Ram Ji),

In this article, I will share one of my recent finding which is basically related to JS files. In which, i will tell you that how these JS files will help you to find a High Severity bugs.

If you are too lazy then I suggest you please use this tool i.e LinkFinder. It’s a tool to discover JS endpoints which is written by GerbenJavado. You can find it here, LinkFinder.

But, I personally prefer doing this stuff as manually. Because sometimes Automated tools don’t come out useful & they skipped out some important things. So, Let’s get Started.

Phase 1: Extracting JS Files & Beautify them :

1. Extract JS Files from source code of redacted.com
2. Bash I used for extracting .js files using waybackurl:

Extraction(){

waybackurl $1| grep -iE “\.js$” | uniq | sort

}

3. For Beautifying the JS Code I used js-beautify for pretty print js code (Quite Easy).

js-beautify <file.js> | tee -a <beautify.js>

You can install it from the given link below:

js-beautifybeautifier.io for nodewww.npmjs.com

Phase 2: Searching for Patterns & Endpoints in JS files:

1. These are few patterns that i use while reading any JS file.

{api_key, api-key, apikey , api , access , AccessToken , gmap , gmaps , algolia_api_key , credentials, etc..}

2. Mapping of Endpoints that you found while reading the JS file. (Important one)

3. Most of the bug hunter’s skip the second point just because they can’t map out the correct endpoints which leads to high severity security bugs & loses their chances to getting High severity bugs.

NOTE: Read every path and try to mapping that endpoints until you succeed. Because JS file contains all the solutions related to mapping of endpoints.

Phase 3. Searching for Respective Documentation:

1. If you found any Rest-Api-Key then go for it’s Api Documentation (search on google about respective Api docs) & understand how it works & how you will use it to gain access of target system.
2. Keyhacks (This will help you for quick exploitation. Because this Repository contain’s 50+ Working Exploitable Endpoints of Different Rest-API-Keys).

Now, lets take a look at my disclosed report where i found a HelpShift-Rest-Api-Key using that i can modified the content of accounts & also i can delete the accounts of redacted.com

Steps to Reproduce (Acc. to Report):

Finding API Key:

1. Go to “https://redacted.com/dist/main.7be5c75d761008c183e6.min.js".
2. Analyzing the JS Code & you will found base64 value in HelfShiftApiKey parameter.

HelpShift Rest API Key

Full Exploitation:

1. Go to “https://apidocs.helpshift.com" & Enter Required details that is needed.
2. You got Swagger API & Successfully Logged In. Now do whatever you want to do.

Note: You can also use curl command :

curl -X PUT — header ‘Content-Type: application/x-www-form-urlencoded’ — header ‘Accept: application/json’ — header ‘Authorization: Basic <base64_API_Key>’ -d ‘username=<username>’ ‘https://api-a.helpshift.com/v1/<domain_name>/users/<profile_id>'

you can get all profile id’s from getUser query.

Timeline:

Bounty Rewarded

Sept 26, 2020 — Reported to private program
Sept 26, 2020 — Report Triaged
Sept 29, 2020 — Vulnerability Fixed
Oct 08, 2020 — Bounty of $5000 USD awarded

Special thanks to nullr3x for this (Big Bad Brother 🤑)