-
Notifications
You must be signed in to change notification settings - Fork 75
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
unable to unzip jar files #18
Comments
Looks like the Go |
i tried to reproduce the problem with other files and figured out, that all files are executable jar's see for reference to reproduce the problem you can take thr jar files from this project like the attached |
@t0xic-coder How did you resolve the problem? I'm seeing the same thing. |
@collegian Just unzip your jar to some directory and pass that directory to scanner. |
I looked a bit more into this and there might be a way to add this.
|
For whatever reason I only now realized that I had code written for the simple "ZIP appended to something else" laying around in various incarnations. @t0xic-coder, @FilipDeVos (or anyone else), could you please give the code in https://github.com/hillu/local-log4j-vuln-scanner/tree/feature/broken-zip a try and tell me that it works for your use-cases? Thanks. |
@hillu I will take a look and try it out later today. |
@FilipDeVos I have pushed the change to the master branch and tagged that in the meantime. Thanks in advance for looking into it, anyway. |
I tested and it works properly. Thank you so much. |
@FilipDeVos Thank you. I guess the issue can be closed then. |
While scanning nested .jar files, the scanner exiting with an error:
./local-log4j-vuln-scanner --exclude /proc /
local-log4j-vuln-scanner - a simple local log4j vulnerability scanner
OUTPUT
cant't open JAR file: /../../../FOO-1.0.0-BAR.jar (size 19165951): zip: not a valid zip file
….
manual unzipping the file work's fine
unzip -l /../../../FOO-1.0.0-BAR.jar
Archive: /../../../FOO-1.0.0-BAR.jar
warning [ /../../../FOO-1.0.0-BAR.jar ]: 8500 extra bytes at beginning or within zipfile
(attempting to process anyway)
The text was updated successfully, but these errors were encountered: