[pcre-dev] [Bug 2776] New: pcre2_match.cin PCRE2 10.23 stac…

Top Page

Reply to this message
Author: admin
Date:  
To: pcre-dev
Subject: [pcre-dev] [Bug 2776] New: pcre2_match.cin PCRE2 10.23 stack-overflow.
https://bugs.exim.org/show_bug.cgi?id=2776

            Bug ID: 2776
           Summary: pcre2_match.cin PCRE2 10.23 stack-overflow.
           Product: PCRE
           Version: 10.23 (PCRE2)
          Hardware: x86-64
                OS: Linux
            Status: NEW
          Severity: bug
          Priority: medium
         Component: Code
          Assignee: Philip.Hazel@???
          Reporter: 670605832@???
                CC: pcre-dev@???


==32276==ERROR: AddressSanitizer: stack-overflow on address 0x7ffc062ae400 (pc
0x0000005f0982 bp 0x7ffc062bc4a0 sp 0x7ffc062ae400 T0)
    #0 0x5f0981 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:578
    #1 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #2 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #3 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #4 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #5 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #6 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #7 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #8 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #9 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #10 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #11 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #12 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #13 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #14 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #15 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #16 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #17 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #18 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #19 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #20 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #21 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #22 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #23 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #24 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #25 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #26 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #27 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #28 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #29 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #30 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #31 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #32 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #33 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #34 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #35 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #36 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #37 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #38 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #39 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #40 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #41 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #42 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #43 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #44 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #45 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #46 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #47 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #48 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #49 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #50 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #51 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #52 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #53 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #54 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #55 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #56 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #57 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #58 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #59 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #60 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #61 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #62 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #63 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #64 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #65 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #66 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #67 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #68 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #69 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #70 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #71 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #72 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #73 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #74 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #75 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #76 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #77 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #78 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #79 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #80 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #81 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #82 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #83 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #84 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #85 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #86 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #87 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #88 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #89 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #90 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #91 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #92 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #93 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #94 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #95 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #96 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #97 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #98 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #99 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #100 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #101 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #102 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #103 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #104 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #105 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #106 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #107 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #108 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #109 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #110 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #111 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #112 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #113 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #114 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #115 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #116 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #117 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #118 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #119 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #120 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #121 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #122 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #123 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #124 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #125 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #126 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #127 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #128 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #129 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #130 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #131 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #132 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #133 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #134 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #135 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #136 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #137 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #138 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #139 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #140 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #141 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #142 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #143 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #144 0x6035fd in match /pcre2-CVE-2017-8786/src/pcre2_match.c:2128:7
    #145 0x5f4302 in match /pcre2-CVE-2017-8786/src/pcre2_match.c:1017:9
    #146 0x5ed895 in pcre2_match_8
/pcre2-CVE-2017-8786/src/pcre2_match.c:6992:8
    #147 0x52350b in process_data /pcre2-CVE-2017-8786/src/pcre2test.c:6606:9
    #148 0x5110c6 in main /pcre2-CVE-2017-8786/src/pcre2test.c:7821:12
    #149 0x7f06d95d982f in __libc_start_main
/build/glibc-LK5gWL/glibc-2.23/csu/../csu/libc-start.c:291
    #150 0x419de8 in _start (/pcre2-CVE-2017-8786/pcre2test+0x419de8)


SUMMARY: AddressSanitizer: stack-overflow
/pcre2-CVE-2017-8786/src/pcre2_match.c:578 in match

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