nicolas/llvm-project
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Verify sizes when trying to read a BitcodeAbbrevOp

Browse Source 
Summary:
Make sure the abbrev operands are valid and that we can read/skip them
afterwards.

Bug found with AFL fuzz.

Reviewers: rafael

Subscribers: llvm-commits

Differential Revision: http://reviews.llvm.org/D9030

llvm-svn: 235595
This commit is contained in:
Filipe Cabecinhas
2015-04-23 13:25:35 +00:00
parent 9316d89d55
commit ee48feadfd
5 changed files with 19 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

BIN
llvm/test/Bitcode/Inputs/invalid-abbrev-fixed-size-too-big.bc Normal file
View File

Binary file not shown.

BIN
llvm/test/Bitcode/Inputs/invalid-abbrev-vbr-size-too-big.bc Normal file
View File

Binary file not shown.

7
llvm/test/Bitcode/invalid.test
View File

@@ -66,3 +66,10 @@ RUN: not llvm-dis -disable-output %p/Inputs/invalid-fp-shift.bc 2>&1 | \
RUN: FileCheck --check-prefix=FP-SHIFT %s
FP-SHIFT: Invalid record
RUN: not llvm-dis -disable-output %p/Inputs/invalid-abbrev-vbr-size-too-big.bc 2>&1 | \
RUN: FileCheck --check-prefix=HUGE-ABBREV-OP %s
RUN: not llvm-dis -disable-output %p/Inputs/invalid-abbrev-fixed-size-too-big.bc 2>&1 | \
RUN: FileCheck --check-prefix=HUGE-ABBREV-OP %s
HUGE-ABBREV-OP: Fixed or VBR abbrev record with size > MaxChunkData