SwitchEmu/breakpad
1
0
Fork 0
mirror of https://git.suyu.dev/suyu/breakpad.git synced 2026-02-28 19:02:57 +00:00
Code Issues Packages Projects Releases Wiki Activity

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
Download Patch File Download Diff File Expand all files Collapse all files

9
src/google_breakpad/processor/exploitability.h
View File

@@ -53,6 +53,15 @@ class Exploitability {
static Exploitability *ExploitabilityForPlatform(Minidump *dump,
ProcessState *process_state);
// The boolean parameter signals whether the exploitability engine is
// enabled to call out to objdump for disassembly. This is disabled by
// default. It is used to check the identity of the instruction that
// caused the program to crash. This should not be enabled if there are
// portability concerns.
static Exploitability *ExploitabilityForPlatform(Minidump *dump,
ProcessState *process_state,
bool enable_objdump);
ExploitabilityRating CheckExploitability();
bool AddressIsAscii(uint64_t);