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

Fix when scan incorrect doc cause memory crash #138

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix when scan incorrect doc cause memory crash #138

wants to merge 1 commit into from

Conversation

BootKitS
Copy link

Fix when scan incorrect doc cause memory crash

When I use mraptor scan a incorrect doc file, that caused memory crash. I followed this code run, find that problem caused in olefiel.py.
crash doc file :https://github.com/BootKitS/hexo/blob/master/file/123.doc

Issus:

Affected tool:
mraptor

Describe the bug
When scan incorrect doc cause memory crash

File sample to reproduce the bug
https://github.com/BootKitS/hexo/blob/master/file/123.doc

How To Reproduce the bug

python mraptor.py 123.doc

Expected behavior
Return result code and exit program.

Console output / Screenshots
1
2
3

Version information:**

  • OS: Windows 10
  • OS version: /64 bits
  • Python version: 3.7.5 64bit
  • oletools version: v0.56

Additional context

Read Much incorrect sector and no exception caught

Fix when scan incorrect doc cause memory  crash
@BootKitS BootKitS changed the title Update olefile.py Fix when scan incorrect doc cause memory crash Oct 17, 2020
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 57.014% when pulling e7c00dc on BootKitS:master into f6315f1 on decalage2:master.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 57.014% when pulling e7c00dc on BootKitS:master into f6315f1 on decalage2:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 57.014% when pulling e7c00dc on BootKitS:master into f6315f1 on decalage2:master.

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

Successfully merging this pull request may close these issues.

None yet

3 participants