-
-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on first installation: java.lang.NumberFormatException: Cannot parse null string #15
Comments
Thank you for reporting this issue. When (e.g. at runtime or upon installation) and how exactly do you get this error though? I remember an old PR #14 that included a similar fix to number conversion issues like this, though I haven't been able to reproduce it myself. I'm pretty sure this isn't related to your Java version. I'll investigate it further, but any more info you can provide is appreciated! |
I pushed some changes that could fix the issue (still couldn't reproduce, so I've made some changes based on what I know), please see the v0.0.2-rc.1 tag or build from source to check if it resolves your issue. EDIT: something seems wrong with the builds, please compile from source for now. EDIT 2: Builds are fixed, try https://github.com/sleeyax/burp-awesome-tls/releases/tag/v0.0.2-rc.2. |
Assuming this is fixed, re-open if you're still experiencing this issue. |
I still have the bug.
|
@xliee can you provide more information on how to reproduce this bug exactly and which operating system you're using. |
Hello, the error just dissapeared and running normally now, but i encountered another issue. Im running windows 11. The issue: I was connecting to https://tls.peet.ws/ after some successful connections to that exact website with the same tls settings Got this logs in the console:
Btw nice work, the extension works great :) |
Yes, please open another issue. |
I ran into this error as well on macOS 12.6 w/ Burp Suite CE v2022.8.4 right after installing. Closing and reopening Burp seemed to solve the problem for me |
Am sorry for the late responses, it been a while since I use the computer
hope you are good. About my environment OS: Archlinux with Java 17
…On Fri, Sep 23, 2022, 4:55 AM Alec Haring, ***@***.***> wrote:
I ran into this error as well on macOS 12.6 w/ Burp Suite CE v2022.8.4
right after installing. Closing and reopening Burp seemed to solve the
problem for me
—
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOCILUFLDJRKNW57KIPBH4DV7UZ3VANCNFSM56OG4PQA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
@root0xa3, try the newest release. If you still get the error, try restarting Burp |
Odd, I have the same setup and still can't reproduce this. I might try again later in a VM just so I can get glimpse of what you're experiencing. Try the suggested work around for now. |
Just tried to install the extension in a Ubuntu 22.04 VM with default setup and got the same error. I finally managed to reproduce this! Seems to only happen upon installation though. Reloading the extension after installation seems to 'fix' the issue. |
I guess it could be related to the Java version then. On Ubuntu, Burp Suite's installer bundles OpenJDK 17:
|
Based on the error traceback, I think it's a race condition with the settings. It's trying to |
Could be, it's just odd that I can never reproduce this on my local install (which actually uses openjdk 19, not 17) and can only reproduce this on ubuntu with the bundled openjdk 17. In fact, the extension doesn't even seem to work at all on ubuntu because the server isn't even starting. That could be a configuration issue on my hand related to permissions, but if it's not there are bigger issues at play here. I will create an other issue for this if the solution doesn't become apparent soon. |
Burp extension settings seem to persist even after the extension is removed. I can do some more investigating tomorrow |
I just reset burp via Anyways, it probably isn't relevant. There should be enough information here to look for the actual cause. |
Did you check to see if your changed extension settings were reverted after doing this? I just tried, and my changes were never reverted. All my Burp extensions were removed, but their settings were not. |
For real? I didn't notice that, oops. Now I wonder if uninstalling/purging burp from the system even removes the extension settings... |
Same issue with Windows 11 JAVA 8.0.3330.2 java.lang.NumberFormatException: Cannot parse null string |
Same issue. Arch linux
|
C:\Users\xxxx>java --version java.lang.NumberFormatException: Cannot parse null string |
For those who are still experiencing this issue: just ignore it and reload the extension. It should work afterwards. I won't fix this until #25 is finished. |
Run java 17.0.4 2022-07-19 LTS and I have tried various versions of Java but none of them works. these are errors. Thanks for your contribution.
java.lang.NumberFormatException: Cannot parse null string
at java.base/java.lang.Integer.parseInt(Integer.java:630)
at java.base/java.lang.Integer.parseInt(Integer.java:786)
at burp.Settings.getTimeout(Settings.java:52)
at burp.SettingsTab.(SettingsTab.java:38)
at burp.BurpExtender.registerExtenderCallbacks(BurpExtender.java:33)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at burp.xu1.lambda$registerExtenderCallbacks$0(Unknown Source)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
The text was updated successfully, but these errors were encountered: