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.

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

Infinite loop when parsing resources #31

Closed
bennw opened this issue Apr 19, 2018 · 5 comments
Closed

Infinite loop when parsing resources #31

bennw opened this issue Apr 19, 2018 · 5 comments

Comments

@bennw
Copy link

bennw commented Apr 19, 2018

manalyze_infloop.zip

CAUTION: malware attached

The file in the attached zip gives an infinite loop when parsing resources, spamming the following error messages:

[*] Warning: The PE contains duplicate resources. It was almost certainly crafted manually.
[*] Warning: Could not locate the section containing resource 65280. Trying to use the RVA as an offset...
[*] Warning: Resource 65280 has a size of 0!

Seems to be related to size 0 resources.

@JusticeRage
Copy link
Owner

Hi! Thanks a lot for the report! I'm a little busy at the moment but I'll look into this file ASAP!

@JusticeRage
Copy link
Owner

JusticeRage commented Apr 24, 2018

I've started looking into this issue. I can confirm that it takes place during the parsing of the resources, but at the moment I'm not sure that there is indeed an infinite loop taking place. It could be that parsing so many resources and printing out all the warnings takes a very long time. Either way, something needs to be done about it!

@bennw
Copy link
Author

bennw commented Apr 25, 2018

Thanks for looking into it! If it helps, at some point during the parsing, the resource number goes to 0:

[*] Warning: The PE contains duplicate resources. It was almost certainly crafted manually.
[*] Warning: Could not locate the section containing resource . Trying to use the RVA as an offset...
[*] Warning: Resource 0 has a size of 0!

I've been running the parser; as of now, the printed warnings are 107 GB in size (and counting!)

@JusticeRage
Copy link
Owner

Integer overflow on the number of resources? I'll be sure to keep that in mind.
On my end, I've launched the parser with all messages disabled hoping that I'll be able to reach the end of the analysis!

@JusticeRage
Copy link
Owner

JusticeRage commented Jun 4, 2018

Okay, Manalyze has been running for weeks on your sample and still doesn't show any signs of stopping. I'm revising my initial judgement: you may have been right that the program somehow enters an infinite loop.
I'll keep investigating this issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants