Add check for Linux minidump ending on bad write for exploitability rating.

Browse source

If a crash occurred as a result to a write to unwritable memory, it is reason
to suggest exploitability. The processor checks for a bad write by
disassembling the command that caused the crash by piping the raw bytes near
the instruction pointer through objdump. This allows the processor to see if
the instruction that caused the crash is a write to memory and where the
target of the address is located.

R=ivanpe@chromium.org

Review URL: https://codereview.chromium.org/1273823004

git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@1497 4c0a9323-5329-0410-9bdc-e9ce6186880e

...

This commit is contained in:

Liu.andrew.x@gmail.com 2015-08-21 16:22:19 +00:00

parent ee2d76fe90

commit f073540795

13 changed files with 584 additions and 8 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

BIN

src/processor/testdata/linux_write_to_outside_module.dmp vendored Normal file

View file

Binary file not shown.