Not working on Windows x64 about burp-awesome-tls

[misssis1]

Restarting didn't change anything

[misssis1]

I also tried the latest versions of 2023, the result is the same

[misssis1]

@sleeyax

[sleeyax]

Try to open https://127.0.0.1:8081/ in a regular browser (click accept risk and continue to ignore the self-signed SSL certificate). It should respond with Awesome TLS error: missing transport configuration. Then you know the Awesome TLS server is running and it's probably an issue with your burp configuration.

[sleeyax]

Ah and in your case maybe you forgot to click save settings (at the bottom)? 8081 is a custom port you configured. Maybe restart burp afterwards to be sure.

[misssis1]

After saving the settings, I clicked and restarted - same result. If I use a normal browser, it doesn't open either:

[misssis1]

If I understand correctly, the Awesome Tls server won't start? What can be done about it? On another computer the problem is the same...

[sleeyax]

Looks like it... Check the extension error log and paste it here if you see anything. Also try a different port like 8887 to be sure.

[misssis1]

[misssis1]

Tried changing ports - same result.

[misssis1]

I didn't need to install any additional software? It was enough to download Burp from the official site (.exe) and your extension and add it, is that correct? Again, the problem is the same on the second computer

[sleeyax]

I just booted a clean Windows 10 VM, installed Burp Suite Community Edition, installed the latest version of Awesome TLS and it just worked out of the box without touching the configuration. So the issue seems to be something odd on your end. Maybe you have an aggressive antivirus or firewall that's blocking the port?

If nothing works and you are up for a challenge, you can try building the server from the source code and run it standalone to see if you get any more detailed errors. Steps:

• clone this repository, open cmd an type:
• cd src/go-server
• go run cmd/main.go
• open burp > awesome TLS settings > change port to the port of the local server (it should be a different port, otherwise it will use the bundled server instead) and save settings
• use burp like usual. you should see logs outputted in cmd

[misssis1]

Another question. I have Windows 10 Pro 22H2. The extension only installs this correctly:

[misssis1]

If I add Burp-Awesome-TLS-fat.jar or Burp-Awesome-TLS-windows-amd64.jar, burp immediately crashes. Although as far as I understand I need to install these versions?

[sleeyax]

Hmm can you share a screenshot of Settings app > System > About > Device specifications (I only need to know System Type).

If it looks like this you should be able to run the amd64 build:

i386 is for 32-bit architectures, which is rather uncommon nowadays.

That being said, I tried to load the i386 build in my Windows VM and finally manged to reproduce the issue you're having :) I suspect that Burps Java runtime tries to load the x64 binary for the server according to your system's architecture, but can't find it and then doesn't do anything. You still see logs in the output log because those are logged from the Java side, but nothing is actually sent to the go side (server) because the server just isn't running.

So, there's actually 2 'issues' to conclude from this:

• We need to figure out why the 64-bit build doesn't work for you
• An error should be logged when the server binary isn't found to prevent confusion like this in the future

[sleeyax]

I created an issue for the latter (feel free to contribute a solution if you want, I'd highly appreciate it!). Let's stick to the former problem in this issue.

[misssis1]

Хм, не могли бы вы поделиться снимком экрана приложения «Настройки» > «Система» > «О программе» > «Характеристики устройства» (мне нужно только знать тип системы).

Если это выглядит так, вы сможете запустить amd64строить:

i386предназначен для 32-битных архитектур, что в настоящее время довольно редко.

That being said, I tried to load the i386 build in my Windows VM and finally manged to reproduce the issue you're having :) I suspect that Burps Java runtime tries to load the x64 binary for the server according to your system's architecture, but can't find it and then doesn't do anything. You still see logs in the output log because those are logged from the Java side, but nothing is actually sent to the go side (server) because the server just isn't running.

So, there's actually 2 'issues' to conclude from this:

* We need to figure out why the 64-bit build doesn't work for you

* An error should be logged when the server binary isn't found to prevent confusion like this in the future

Hmm can you share a screenshot of Settings app > System > About > Device specifications (I only need to know System Type).

If it looks like this you should be able to run the amd64 build:

i386 is for 32-bit architectures, which is rather uncommon nowadays.

That being said, I tried to load the i386 build in my Windows VM and finally manged to reproduce the issue you're having :) I suspect that Burps Java runtime tries to load the x64 binary for the server according to your system's architecture, but can't find it and then doesn't do anything. You still see logs in the output log because those are logged from the Java side, but nothing is actually sent to the go side (server) because the server just isn't running.

So, there's actually 2 'issues' to conclude from this:

* We need to figure out why the 64-bit build doesn't work for you

* An error should be logged when the server binary isn't found to prevent confusion like this in the future

[misssis1]

1. Installed the latest version of Burp Community Edition
2. Downloaded the Burp-Awesome-TLS-windows-amd64.jar extension
3. Didn't change any settings at all, added the plugin - it added, but the errors stated the following:

java.lang.NumberFormatException: Cannot parse null string
at java.base/java.lang.Integer.parseInt(Integer.java:627)
at java.base/java.lang.Integer.parseInt(Integer.java:781)
at burp.Settings.getHttpTimeout(Settings.java:68)
at burp.SettingsTab.(SettingsTab.java:44)
at burp.BurpExtender.registerExtenderCallbacks(BurpExtender.java:33)
at burp.Zprt.Zw(Unknown Source)
at burp.Zyup.Zk(Unknown Source)
at burp.Zyut.lambda$initializeOnNewThread$0(Unknown Source)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577)
at java.base/java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317)
at java.base/java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1623)

4. I restart Burp - the plugin is not active! I add it again, Burp crashes immediately after adding it.
5. Contents of the application log during Burp crash:
   

[misssis1]

1. Installed the latest version of Burp Community Edition

   2. Downloaded the Burp-Awesome-TLS-windows-amd64.jar extension

   3. Didn't change any settings at all, added the plugin - it added, but the errors stated the following:

java.lang.NumberFormatException: Cannot parse null string at java.base/java.lang.Integer.parseInt(Integer.java:627) at java.base/java.lang.Integer.parseInt(Integer.java:781) at burp.Settings.getHttpTimeout(Settings.java:68) at burp.SettingsTab.(SettingsTab.java:44) at burp.BurpExtender.registerExtenderCallbacks(BurpExtender.java:33) at burp.Zprt.Zw(Unknown Source) at burp.Zyup.Zk(Unknown Source) at burp.Zyut.lambda$initializeOnNewThread$0(Unknown Source) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577) at java.base/java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) at java.base/java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1623)

4. I restart Burp - the plugin is not active! I add it again, Burp crashes immediately after adding it.

5. Contents of the application log during Burp crash:
   ![2](https://user-images.githubusercontent.com/151674518/285011290-570d5381-1e24-4872-9b9a-b974264af22a.png)

Before all these actions was restored win 10 image on which Burp was never installed

[misssis1]

1. Установлена ​​последняя версия Burp Community Edition.

   2. Скачал расширение Burp-Awesome-TLS-windows-amd64.jar.

   3. Никаких настроек вообще не менял, добавил плагин - добавилось, но ошибки выдавали следующее:

java.lang.NumberFormatException: невозможно проанализировать нулевую строку в java.base/java.lang.Integer.parseInt(Integer.java:627) в java.base/java.lang.Integer.parseInt(Integer.java:781) в burp.Settings.getHttpTimeout(Settings.java:68) в Burp.SettingsTab.(SettingsTab.java:44) в burp.BurpExtender.registerExtenderCallbacks(BurpExtender.java:33) в burp.Zprt.Zw (неизвестный источник) в burp.Zyup.Zk (неизвестный источник) в burp.Zyut.lambda$initializeOnNewThread$0 (неизвестный источник) в java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577) в java.base/java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) в java.base/java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) в java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) в java.base/java.lang.Thread.run(Thread.java:1623)

4. Перезапускаю Burp - плагин не активен!  Добавляю еще раз, Burp вылетает сразу после добавления.

5. Содержимое журнала приложения во время сбоя Burp: 
   ![2](https://user-images.githubusercontent.com/151674518/285011290-570d5381-1e24-4872-9b9a-b974264af22a.png)

1. Installed the latest version of Burp Community Edition

   2. Downloaded the Burp-Awesome-TLS-windows-amd64.jar extension

   3. Didn't change any settings at all, added the plugin - it added, but the errors stated the following:

java.lang.NumberFormatException: Cannot parse null string at java.base/java.lang.Integer.parseInt(Integer.java:627) at java.base/java.lang.Integer.parseInt(Integer.java:781) at burp.Settings.getHttpTimeout(Settings.java:68) at burp.SettingsTab.(SettingsTab.java:44) at burp.BurpExtender.registerExtenderCallbacks(BurpExtender.java:33) at burp.Zprt.Zw(Unknown Source) at burp.Zyup.Zk(Unknown Source) at burp.Zyut.lambda$initializeOnNewThread$0(Unknown Source) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:577) at java.base/java.base/java.util.concurrent.FutureTask.run(FutureTask.java:317) at java.base/java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) at java.base/java.lang.Thread.run(Thread.java:1623)

4. I restart Burp - the plugin is not active! I add it again, Burp crashes immediately after adding it.

5. Contents of the application log during Burp crash:
   ![2](https://user-images.githubusercontent.com/151674518/285011290-570d5381-1e24-4872-9b9a-b974264af22a.png)

5 para, text:
Faulting application name: BurpSuiteCommunity.exe, version: 2023.10.3.6, time stamp: 0x647f32a9
Faulting module name: jna715638035215112812.dll, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80000003
Fault offset: 0x0000000000066541
Faulting process id: 0x53c
Faulting application start time: 0x01da1d74ebcdc148
Faulting application path: C:\Program Files\BurpSuiteCommunity\BurpSuiteCommunity.exe
Faulting module path: C:\Users\user\AppData\Local\Temp\jna-3599307\jna715638035215112812.dll
Report Id: b94e2b58-f413-4015-a364-2d220f5486cb
Faulting package full name:
Faulting package-relative application ID:

[sleeyax]

Hmm I'm running out of ideas here 🤔. We're both running the same architecture for the VM but on your end something goes wrong with Burps JNA (Java Native Access), presumably when it tries to resolve the bundled server dll.

Maybe you can figure out more by compiling the jar manually from source? And perhaps slightly modify the Java source to add some log statements around the parts that load the server dll? Compilation instructions are at the bottom of the README. Unfortunately I can't do this myself as I can't reproduce this issue on any of my machines.

[misssis1]

Hmm I'm running out of ideas here 🤔. We're both running the same architecture for the VM but on your end something goes wrong with Burps JNA (Java Native Access), presumably when it tries to resolve the bundled server dll.

Maybe you can figure out more by compiling the jar manually from source? And perhaps slightly modify the Java source to add some log statements around the parts that load the server dll? Compilation instructions are at the bottom of the README. Unfortunately I can't do this myself as I can't reproduce this issue on any of my machines.

Unfortunately, I can't get through this manual

[misssis1]

In a virtual machine on win 7 everything works successfully, I will probably reinstall the windows 10 build

[sleeyax]

Ok, let me know how it goes!

[sleeyax]

And if you need help with building from source let me know. You can also message me on social media (preferably discord or telegram) if that's easier. But if you have no experience in coding I must admit it will be difficult to help you.

[misssis1]

I figured out the reason why the plugin wasn't working for me. And so:
Was installed Windows 10 on a virtual machine - no problems, the plugin works as it should! The same Windows is installed on a physical machine:
Gigabyte Z77 DS3h motherboard rev. 1.0
GTX 1080TI EVGA graphics card
On the freshly installed Windows, only the chipset and NVIDIA drivers were installed. I do all the same as described above - the program closes the error in the log is the same. I uninstall the NVIDIA driver - everything works at once! As a result, the NVIDIA driver was installed from the Windows Update Center, with this scheme everything works. Conclusion: installing NVIDIA driver for GTX 1080TI EVGA from the official site - we get a plugin that doesn't work - in my case when adding the Burp plugin there was a failure! Solution: install the driver through Windows Update Center. Link to the driver with which the plugin did not work for me:
https://www.nvidia.com/ru-ru/geforce/drivers/results/216428/

[misssis1]

And so the last thing I did, restored the Windows 10 image (from the first post) uninstalled the NVIDIA driver and installed it through the Windows Update Center, after that I got it working!!!!

[sleeyax]

I'm glad you figured it out! Windows can do crazy things sometimes...

[sleeyax]

Closing as a solution has been found.

[milled-steel]

Wanted to add this issue isn't a one off and I get the same exact crash with an MSI GTX 1080 Ti using the 64 bit jar file

[sleeyax]

Wanted to add this issue isn't a one off and I get the same exact crash with an MSI GTX 1080 Ti using the 64 bit jar file

Have you tried fixing it in a similar way to the other user? If that doesn't work I'll need more details about your system because I can't reproduce this. Alternatively, try to build the extension from source and see what that does for you.