https://bugs.exim.org/show_bug.cgi?id=2775
Bug ID: 2775
Summary: pcre_exec.c in PCRE 8.40 allows remote attackers to
cause stack-overflow.
Product: PCRE
Version: 8.40
Hardware: x86-64
OS: Linux
Status: NEW
Severity: bug
Priority: medium
Component: Code
Assignee: Philip.Hazel@???
Reporter: 670605832@???
CC: pcre-dev@???
==40049==ERROR: AddressSanitizer: stack-overflow on address 0x7ffc02a50340 (pc
0x0000005bb01f bp 0x7ffc02a55b80 sp 0x7ffc02a50340 T0)
#0 0x5bb01e in match /pcre-CVE-2017-7186/pcre_exec.c:516
#1 0x5bdbaa in match /pcre-CVE-2017-7186/pcre_exec.c:879:7
#2 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#3 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#4 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#5 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#6 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#7 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#8 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#9 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#10 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#11 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#12 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#13 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#14 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#15 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#16 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#17 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#18 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#19 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#20 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#21 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#22 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#23 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#24 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#25 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#26 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#27 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#28 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#29 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#30 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#31 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#32 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#33 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#34 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#35 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#36 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#37 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#38 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#39 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#40 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#41 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#42 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#43 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#44 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#45 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#46 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#47 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#48 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#49 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#50 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#51 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#52 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#53 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#54 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#55 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#56 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#57 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#58 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#59 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#60 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#61 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#62 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#63 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#64 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#65 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#66 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#67 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#68 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#69 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#70 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#71 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#72 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#73 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#74 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#75 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#76 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#77 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#78 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#79 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#80 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#81 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#82 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#83 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#84 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#85 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#86 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#87 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#88 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#89 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#90 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#91 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#92 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#93 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#94 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#95 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#96 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#97 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#98 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#99 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#100 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#101 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#102 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#103 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#104 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#105 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#106 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#107 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#108 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#109 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#110 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#111 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#112 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#113 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#114 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#115 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#116 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#117 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#118 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#119 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#120 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#121 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#122 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#123 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#124 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#125 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#126 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#127 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#128 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#129 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#130 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#131 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#132 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#133 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#134 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#135 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#136 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#137 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#138 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#139 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#140 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#141 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#142 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#143 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#144 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#145 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#146 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#147 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#148 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#149 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#150 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#151 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#152 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#153 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#154 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#155 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#156 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#157 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#158 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#159 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#160 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#161 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#162 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#163 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#164 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#165 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#166 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#167 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#168 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#169 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#170 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#171 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#172 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#173 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#174 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#175 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#176 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#177 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#178 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#179 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#180 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#181 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#182 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#183 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#184 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#185 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#186 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#187 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#188 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#189 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#190 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#191 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#192 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#193 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#194 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#195 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#196 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#197 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#198 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#199 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#200 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#201 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#202 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#203 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#204 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#205 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#206 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#207 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#208 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#209 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#210 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#211 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#212 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#213 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#214 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#215 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#216 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#217 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#218 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#219 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#220 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#221 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#222 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#223 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#224 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#225 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#226 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#227 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#228 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#229 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#230 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#231 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#232 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#233 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#234 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#235 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#236 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#237 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#238 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#239 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#240 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#241 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#242 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#243 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#244 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#245 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#246 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#247 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#248 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#249 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
#250 0x5bea31 in match /pcre-CVE-2017-7186/pcre_exec.c:935:7
SUMMARY: AddressSanitizer: stack-overflow /pcre-CVE-2017-7186/pcre_exec.c:516
in match
==40049==ABORTING
--
You are receiving this mail because:
You are on the CC list for the bug.
