Bypassing E2E encryption leads to multiple high vulnerabilities.

In today’s blog, I’m going to show you how I was able to bypass the E2E encryption of an application by analyzing an obfuscated javascript file that was imported to that application, and how this helped me to better understand the internals of this application and get to find other multiple high vulnerabilities.


As you can see, I can’t find the real body that was sent to the API, can’t find any parameters, all were encrypted!

That is a type of E2E (End-2-End) encryption, where the communication between the client and the server is encrypted, this is an extra security layer to protect against any type of middle attacks.

All requests are initiated from our browser, right? so any kind of encryption or encoding that is performed on the request body would be done on the client side, so javascript files will be our target.

Javascript Files Analysis— First Round:

messy javascript file

To find something here is similar to digging for the needle in the haystack, but let’s give it a try!

If we look at what we have, we only have the JSON body that has these key/pairs v, iv, keys, and cipher. All these keys are changeable for every request except the v key, its value is still the same for every request, which is “pef2.

As this value is fixed (didn’t change in every request), so for sure it would be defined somewhere in the js file, if I found it, maybe it would lead us to the function that performs this encryption.

searching in javascript to guide us to the function that encrypts the request body

As expected, it was mentioned just once, but I spent some time searching and debugging, following the initiators (it was more than 55 called functions), I figured out how a couple of functions work but it wasn't helpful to my goal (finding where the encryption/decryption is done).

I needed any word or function name to search for in this js file to speed up the reversing process, so I tried to find the old version of this file in the internet archive maybe it wasn’t obfuscated, but no luck.

Who else is using the same API?

decompiling the APK

I decompiled the APK with apktool and then started to search for the same word -“pef2”- inside the whole application files.

I found a new js file called “” containing this word, after opening this file with a js-beautifier tool, and thankfully it was not obfuscated!

As you can see, “pef2” is mentioned in line 106568, and this string is mentioned in a function called “encrypt”.

We can use some words mentioned in this function and search for them in the JS file on the web application, just to focus more on our main target which is the web application.

I searched for new words like getBytesSync, RSA-OAEP , and of course encrypt .

Back to the main goal — Second Round:

making the code more readable

I ended up with a function called “encrypt” in line 137777, and as you can see above, this function takes 2 arguments, let’s add a breakpoint to pause the JS execution and inspect this function and check what is going on.

Adding breakpoints

After initiating a random request to invoke the breakpoint, I found the following

checking the DOM after invoking the breakpoint

One of the arguments of encrypt function is _0x3fc2ff, and its value as you can see in the Scope section is a JSON object, so let’s move to the console to fully understand its components.

As the breakpoint is on, we can print and perform actions while the application paused.

Analyzing the data passed to the “encrypt” function:

original request body

A JSON object contains multiple keys/values that the API uses to handle the requests, so this is the original request body before any type of encryption.

The request is sent to /v1/user API endpoint with two parameters domain and user , and returns all information about this user as you can see below

returned data from the request

As you may guess, we can test for IDOR in the user parameter, let’s change it to another username and check the response!

and the result was promising!

IDOR confirmed

Great! a valid IDOR vulnerability was confirmed, after digging more, I found multiple other IDORs that lead me to edit any user information like email and phone number, etc.

What about the url parameter?

What came to my mind is to test for SSRF in the url parameter, so I changed its value to my burp collaborator to check if we can get an internal interaction.

{"url":"/v1/user","method":"get","headers":{"common":{"Accept":"application/json, text/plain, */*"},"delete":{},"get":{},"head":{},"post":{"Content-Type":"application/x-www-form-urlencoded"},"put":........}

Changed to:

{"url":"","method":"get","headers":{"common":{"Accept":"application/json, text/plain, */*"},"delete":{},"get":{},"head":{},"post":{"Content-Type":"application/x-www-form-urlencoded"},"put":........}
SSRF confirmed

As you can see, I forward the request, then got an interaction!

What should I do if I couldn’t reach to the original JS file?

Now let’s assume that there is no android application at all and no original js files, and we need to bypass it!

We can make use of the Event Listener Breakpoints tap in the browser’s dev tools which helps us to add breakpoints to pause the application when event listeners are hit/fired, we can select specific events, such as load, and error, etc.

The event that will be useful for us is click, so when we click on any button that initiates an API request the execution pauses, and the source panel displays the highlighted line of the JavaScript code that is next to be executed, along with the surrounding code for context. In addition, we have buttons to step over that line of code or resume execution.

Setting up Event Listener Breakpoints

I selected click event and then I clicked a button that initiates an API request, the execution paused, and then I used the step-over buttons till I reach a function that takes the full request body!

But as expected, it takes a bit of time to reach it.
Now again, I can edit the request before being encrypted.

This application is large, and editing every request with this method is a waste of time!

So we need to find a method to be able to intercept the requests easily, (e.g. with burp suite), and to do so, we have two options:

  • Understand how the application encrypts the request body and finds a way to decrypt it.
  • Edit the javascript file and run our own file.

The first option will take a long time especially since the file is obfuscated, so let’s stick to the second option.

We can use the override feature to do that, with override, we can take a resource from the current webpage and store it locally. When you refresh the webpage, the browser doesn’t load the resource from the server. Instead, the browser replaces the server resource with your local copy of the resource.

We are now ready to edit this file, so the next step is to add some kind of a middle layer (e.g. proxy) into this function to make it encrypt our edited input, not the value that the application passes to the function.

We can do this in more than one way, but let’s keep it simple.
I launched my localhost, and created a simple PHP file that maps the request body to the response, just like below:


# to allow cross origin requests.
header("Access-Control-Allow-Origin: https://█████████████");
header("Access-Control-Allow-Credentials: true");
header("Content-Type: application/json; charset=UTF-8");
header("Access-Control-Allow-Methods: POST");

# get the request body as it is
$data = file_get_contents("php://input");

# return it back
echo $data;


So the idea is:

  • When the application calls the “encrypt” function, it passes two arguments, one of which is the original body.
  • We send a request to our PHP file with the original body, so we can edit it via burp. (Note that we should allow cross-origin requests)
  • The PHP file will return our edited body.
  • We pass the response to the next step in the encrypt function.

I created the following asynchronous function that sends the request to our proxy and returns the edited response:

async function editBeforeSend(originalBody) {
const req = await fetch("http://proxy.melotover.local/editBeforeSend.php",
method: "POST",
body: originalBody,
credentials: 'include'
let editedBody = await req.text();
return editedBody;

I added it to the javascript file, then called it inside encrypt function

That's it! I saved the file, refreshed the page, and invoked any request to the API

Now I control any request body sent to the application just by editing it via burp.

That’s all for this blog, I hope you enjoyed reading and I will be pleased if you have any feedback!



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
Asem Eleraky

Computer Engineering Student | Bug Hunter | CTF Player | AKA Melotover