Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Could not execute GrokAssembly Premature end of file #1464

Closed
razeitona opened this issue Aug 28, 2018 · 15 comments
Closed

Could not execute GrokAssembly Premature end of file #1464

razeitona opened this issue Aug 28, 2018 · 15 comments
Assignees
@jeremylong
Labels
bug
Milestone
6.0.0

Comments

@razeitona
Copy link

Hi,

I've downloaded the latest version of Dependecy Check (3.3.1) and already tried also with one previous version (3.0.2) after tested with 3.3.1 and I'm getting the error related with GrokAssembly

Log:
https://gist.github.com/razeitona/2b1d4d96d5f68b36756479d3e8aecd35

DEBUG - Initializing Assembly Analyzer
2018-08-28 10:07:55,534 org.owasp.dependencycheck.analyzer.AssemblyAnalyzer:223
DEBUG - Extracted GrokAssembly.exe to C:\Users\RICARD~1\AppData\Local\Temp\dctempaf03cfe4-0d44-4885-9f18-3d5515cb646a\GKA11409347276140118492.exe
2018-08-28 10:07:55,535 org.owasp.dependencycheck.analyzer.AssemblyAnalyzer:226
DEBUG - Extracted GrokAssembly.exe.config to C:\Users\RICARD~1\AppData\Local\Temp\dctempaf03cfe4-0d44-4885-9f18-3d5515cb646a\GKA11409347276140118492.exe.config
2018-08-28 10:07:55,676 org.owasp.dependencycheck.analyzer.AssemblyAnalyzer:273
WARN  - An error occurred with the .NET AssemblyAnalyzer;
this can be ignored unless you are scanning .NET DLLs. Please see the log for more details.
2018-08-28 10:07:55,678 org.owasp.dependencycheck.analyzer.AssemblyAnalyzer:275
DEBUG - Could not execute GrokAssembly Premature end of file.
2018-08-28 10:07:55,678 org.owasp.dependencycheck.Engine:819
ERROR - Exception occurred initializing Assembly Analyzer.
2018-08-28 10:07:55,682 org.owasp.dependencycheck.Engine:820
DEBUG - 
org.owasp.dependencycheck.exception.InitializationException: An error occurred with the .NET AssemblyAnalyzer
	at org.owasp.dependencycheck.analyzer.AssemblyAnalyzer.prepareFileTypeAnalyzer(AssemblyAnalyzer.java:277)
	at org.owasp.dependencycheck.analyzer.AbstractFileTypeAnalyzer.prepareAnalyzer(AbstractFileTypeAnalyzer.java:73)
	at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.prepare(AbstractAnalyzer.java:108)
	at org.owasp.dependencycheck.Engine.initializeAnalyzer(Engine.java:817)
	at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:662)
	at org.owasp.dependencycheck.App.runScan(App.java:253)
	at org.owasp.dependencycheck.App.run(App.java:184)
	at org.owasp.dependencycheck.App.main(App.java:69)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
	at java.xml/com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
	at java.xml/com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
	at java.xml/javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
	at org.owasp.dependencycheck.analyzer.AssemblyAnalyzer.prepareFileTypeAnalyzer(AssemblyAnalyzer.java:259)
	... 7 common frames omitted
@jeremylong
Copy link
Owner

Are you analyzing any DLLs or EXEs?

@razeitona
Copy link
Author

A folder with dll.
It was first time that I used Dependency Check, later I've installed on a different machine (also for the first time) and worked without any problem.

@jeremylong
Copy link
Owner

So can this issue be closed?

@razeitona
Copy link
Author

No, because I still can't run in my machine. In 2 of 3 machines that I tested just run in one.

@jeremylong
Copy link
Owner

On the machine where this fails - is the .NET runtime (or mono) installed? The current dependency-check does not support .NET core yet. We will switch to .NET core in the 4.x release.

What output do you get if you download the GrokAssemble.exe and GrokAssemble.exe.config and run GrokAssembly on itself?

./GrokAssembly.exe ./GrokAssembly.exe

@jeremylong
Copy link
Owner

Can you try 5.0.0-M2 - I believe this should be resolved.

@metareven
Copy link

metareven commented Oct 22, 2019 •
edited
Loading

I have a very similar issue on version 5.2.2 with dotnet core 3.0.100 installed

org.owasp.dependencycheck.exception.InitializationException: An error occurred with the .NET AssemblyAnalyzer
	at org.owasp.dependencycheck.analyzer.AssemblyAnalyzer.prepareFileTypeAnalyzer(AssemblyAnalyzer.java:403)
	at org.owasp.dependencycheck.analyzer.AbstractFileTypeAnalyzer.prepareAnalyzer(AbstractFileTypeAnalyzer.java:83)
	at org.owasp.dependencycheck.analyzer.AbstractAnalyzer.prepare(AbstractAnalyzer.java:102)
	at org.owasp.dependencycheck.Engine.initializeAnalyzer(Engine.java:842)
	at org.owasp.dependencycheck.Engine.analyzeDependencies(Engine.java:678)
	at org.owasp.dependencycheck.App.runScan(App.java:251)
	at org.owasp.dependencycheck.App.run(App.java:183)
	at org.owasp.dependencycheck.App.main(App.java:80)
Caused by: org.owasp.dependencycheck.xml.assembly.GrokParseException: org.xml.sax.SAXException: Line=1, Column=1: Premature end of file.
	at org.owasp.dependencycheck.xml.assembly.GrokParser.parse(GrokParser.java:103)
	at org.owasp.dependencycheck.analyzer.AssemblyAnalyzer.prepareFileTypeAnalyzer(AssemblyAnalyzer.java:380)
	... 7 common frames omitted
Caused by: org.xml.sax.SAXException: Line=1, Column=1: Premature end of file.
	at org.owasp.dependencycheck.xml.assembly.GrokErrorHandler.fatalError(GrokErrorHandler.java:71)
	at java.xml/com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:181)
	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400)
	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1471)
	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1013)
	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:605)
	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:112)
	at java.xml/com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:534)
	at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:888)
	at java.xml/com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:824)
	at java.xml/com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
	at java.xml/com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1216)
	at java.xml/com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:635)
	at org.owasp.dependencycheck.xml.assembly.GrokParser.parse(GrokParser.java:92)
	... 8 common frames omitted

@gruselglatz
Copy link

Same problem here, do you have a solution for this?
Same Version of dep. check and dotnet core. On Windows 10

@stevehipwell
Copy link

@metareven @gruselglatz same here!

@metareven
Copy link

At least the docker image works, so use that as a workaround if you need to use this tool

@stevehipwell
Copy link

It looks like DependencyCheck requires DotNet Core v2. I don't think this is a bug but I do think that it should be made clearer. If you install the DotNet Core v2 run-time then the scanner should run successfully. I've tested this solution works in a DotNet Core v3 Docker image by installing the DotNet Core v2.2.7 run-time.

@stevehipwell stevehipwell mentioned this issue Nov 5, 2019
Closed
@RemcoTukker
Copy link

Would be great if it worked out of the box with dotnet core 3 as well

@JStyle21 JStyle21 mentioned this issue Jan 2, 2020
Closed
@stevehipwell
Copy link

@jeremylong could you confirm which version of dotnet needs to be present as v2.2 is out of support?

@jeremylong
Copy link
Owner

I'll re-compile to dotnet 3 with the next release.

@jeremylong jeremylong self-assigned this Apr 2, 2020
@stevehipwell
Copy link

Thanks @jeremylong I assume you specifically mean .NET Core v3.1 which is the current LTS.

jeremylong added a commit that referenced this issue Apr 3, 2020
@jeremylong
upgrade to dotnet 3.1 per #1464
dfd8a4d
@jeremylong jeremylong mentioned this issue Apr 4, 2020
Merged
@jeremylong jeremylong added this to the 5.4.0 milestone Apr 4, 2020
jeremylong added a commit that referenced this issue Apr 5, 2020
@jeremylong
Dotnet upgrade (#2574)
f0533ef 
* upgrade to dotnet 3.1 per #1464
@lock lock bot locked and limited conversation to collaborators May 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremylong jeremylong

Labels
bug
Projects
None yet
Milestone
6.0.0
Development

No branches or pull requests
6 participants
@jeremylong @metareven @RemcoTukker @stevehipwell @razeitona @gruselglatz