[pcre-dev] [Bug 1915] New: Global Variable Buffer Overflow i…

Top Page
Delete this message
Author: admin
Date:  
To: pcre-dev
New-Topics: [pcre-dev] [Bug 1915] Global Variable Buffer Overflow in pcre2test
Subject: [pcre-dev] [Bug 1915] New: Global Variable Buffer Overflow in pcre2test
https://bugs.exim.org/show_bug.cgi?id=1915

            Bug ID: 1915
           Summary: Global Variable Buffer Overflow in pcre2test
           Product: PCRE
           Version: N/A
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Code
          Assignee: ph10@???
          Reporter: fumfi.255@???
                CC: pcre-dev@???


Created attachment 935
--> https://bugs.exim.org/attachment.cgi?id=935&action=edit
POC to trigger global buffer overflow (pcre2test)

Affected:
- pcre2test in PCRE2 version 10.23-RC1 2016-08-01 (SVN revision: 597)
- pcre2test in PCRE2 version 10.22 (Faulty code line: pcre2test.c:3510)

To reproduce the problem (pcre2test):
pcre2test pcre2test_gbo /dev/null

ASAN Output (SVN Revision: 593):

==21946==ERROR: AddressSanitizer: global-buffer-overflow on address
0x0000013c85f8 at pc 0x0000004fdfa8 bp 0x7ffe4d81ef70 sp 0x7ffe4d81ef68
WRITE of size 1 at 0x0000013c85f8 thread T0
    #0 0x4fdfa7 in decode_modifiers XYZ/pcre/src/pcre2test.c:3564:17
    #1 0x4ed5b1 in process_data XYZ/pcre/src/pcre2test.c:6032:20
    #2 0x4ed5b1 in main XYZ/pcre/src/pcre2test.c:7745
    #3 0x7f8f4372482f in __libc_start_main
(/lib/x86_64-linux-gnu/libc.so.6+0x2082f)
    #4 0x41aa78 in _start (/usr/local/bin/pcre2test+0x41aa78)


0x0000013c85f8 is located 0 bytes to the right of global variable 'dat_datctl'
defined in 'src/pcre2test.c:818:15' (0x13c84a0) of size 344
SUMMARY: AddressSanitizer: global-buffer-overflow
XYZ/pcre/src/pcre2test.c:3564:17 in decode_modifiers
Shadow bytes around the buggy address:
  0x000080271060: f9 f9 f9 f9 00 00 00 00 00 00 00 00 00 00 00 00
  0x000080271070: 00 00 00 00 00 00 00 00 f9 f9 f9 f9 00 f9 f9 f9
  0x000080271080: f9 f9 f9 f9 04 f9 f9 f9 f9 f9 f9 f9 01 f9 f9 f9
  0x000080271090: f9 f9 f9 f9 00 00 00 00 00 00 00 00 00 00 00 00
  0x0000802710a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x0000802710b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00[f9]
  0x0000802710c0: f9 f9 f9 f9 f9 f9 f9 f9 00 00 00 00 00 00 00 00
  0x0000802710d0: 00 00 00 00 00 00 00 00 00 00 00 00 f9 f9 f9 f9
  0x0000802710e0: 00 f9 f9 f9 f9 f9 f9 f9 04 f9 f9 f9 f9 f9 f9 f9
  0x0000802710f0: 01 f9 f9 f9 f9 f9 f9 f9 00 f9 f9 f9 f9 f9 f9 f9
  0x000080271100: 04 f9 f9 f9 f9 f9 f9 f9 04 f9 f9 f9 f9 f9 f9 f9
Shadow byte legend (one shadow byte represents 8 application bytes):
  Addressable:           00
  Partially addressable: 01 02 03 04 05 06 07
  Heap left redzone:       fa
  Heap right redzone:      fb
  Freed heap region:       fd
  Stack left redzone:      f1
  Stack mid redzone:       f2
  Stack right redzone:     f3
  Stack partial redzone:   f4
  Stack after return:      f5
  Stack use after scope:   f8
  Global redzone:          f9
  Global init order:       f6
  Poisoned by user:        f7
  Container overflow:      fc
  Array cookie:            ac
  Intra object redzone:    bb
  ASan internal:           fe
  Left alloca redzone:     ca
  Right alloca redzone:    cb
==21946==ABORTING



Regards,
Kamil Frankowicz

--
You are receiving this mail because:
You are on the CC list for the bug.