[pcre-dev] [Bug 1866] New: UTF-8 class containing \D and \P{Nd} matches incorrectly

https://bugs.exim.org/show_bug.cgi?id=1866 Bug ID: 1866 Summary: UTF-8 class containing \D and \P{Nd} matches incorrectly Product: PCRE Version: 8.39 Hardware: x86 OS: All Status: NEW

[pcre-dev] [Bug 1854] New: Null pointer dereference in pcretest

https://bugs.exim.org/show_bug.cgi?id=1854 Bug ID: 1854 Summary: Null pointer dereference in pcretest Product: PCRE Version: 8.39 Hardware: x86 OS: Linux Status: NEW Severity: security Priority:

[pcre-dev] [Bug 1854] Null pointer dereference in pcretest

https://bugs.exim.org/show_bug.cgi?id=1854 --- Comment #3 from bshas...@sec.t-labs.tu-berlin.de --- Created attachment 905 --> https://bugs.exim.org/attachment.cgi?id=905=edit Crashing input #2 -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 1854] Null pointer dereference in pcretest

https://bugs.exim.org/show_bug.cgi?id=1854 --- Comment #4 from bshas...@sec.t-labs.tu-berlin.de --- Created attachment 906 --> https://bugs.exim.org/attachment.cgi?id=906=edit Crashing input #3 -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 1854] Null pointer dereference in pcretest

https://bugs.exim.org/show_bug.cgi?id=1854 --- Comment #2 from bshas...@sec.t-labs.tu-berlin.de --- Created attachment 904 --> https://bugs.exim.org/attachment.cgi?id=904=edit Crashing input #1 Crashing input #1 -- You are receiving this mail because: You are on the CC list for the bug. --

[pcre-dev] [Bug 1854] Null pointer dereference in pcretest

https://bugs.exim.org/show_bug.cgi?id=1854 bshas...@sec.t-labs.tu-berlin.de changed: What|Removed |Added CC||bshas...@sec.t-labs.tu-berl

[pcre-dev] [Bug 1681] CMake compiles PCRE dynamically even when set to static

https://bugs.exim.org/show_bug.cgi?id=1681 Orvid King changed: What|Removed |Added CC||blah38...@gmail.com ---

[pcre-dev] [Bug 1875] New: Options set in the pattern aren't being "globalized" anymore

https://bugs.exim.org/show_bug.cgi?id=1875 Bug ID: 1875 Summary: Options set in the pattern aren't being "globalized" anymore Product: PCRE Version: N/A Hardware: All OS: All Status: NEW

[pcre-dev] [Bug 2030] Exact match mode

https://bugs.exim.org/show_bug.cgi?id=2030 --- Comment #2 from Giuseppe D'Angelo --- Hi, no need to hurry, it's just a suggestion... Regarding your approach of anchoring the match: the problem I see with it is that it may simply fail depending on the nature of the pattern

[pcre-dev] [Bug 2030] Exact match mode

https://bugs.exim.org/show_bug.cgi?id=2030 --- Comment #3 from Philip Hazel --- No, you are right. I had thought about this some more myself, and came to the same conclusion. I will add a new option (called PCRE2_ENDANCHORED unless I can think of something better) that

[pcre-dev] [Bug 2030] Exact match mode

https://bugs.exim.org/show_bug.cgi?id=2030 --- Comment #1 from Philip Hazel --- Thank you for your suggestion. Unfortunately, it is too late for 10.23, for which a Release Candidate is currently available for testing. However, I'm not sure if the feature you ask for is

[pcre-dev] [Bug 1848] pcregrep outputs duplicate matches

https://bugs.exim.org/show_bug.cgi?id=1848 Eric Hoffman changed: What|Removed |Added Resolution|FIXED |---

[pcre-dev] [Bug 1848] pcregrep outputs duplicate matches

https://bugs.exim.org/show_bug.cgi?id=1848 Eric Hoffman changed: What|Removed |Added CC||ehoff...@videotron.ca ---

[pcre-dev] [Bug 2030] Exact match mode

https://bugs.exim.org/show_bug.cgi?id=2030 --- Comment #4 from Giuseppe D'Angelo --- Many thanks for the insight :) Out of curiosity what is that makes an anchored match NOT use the JIT when passed at match time rather than compile time? -- You are receiving this mail

[pcre-dev] [Bug 2023] New: CMake error: option called with incorrect number if arguments

https://bugs.exim.org/show_bug.cgi?id=2023 Bug ID: 2023 Summary: CMake error: option called with incorrect number if arguments Product: PCRE Version: 8.40 Hardware: All OS: Windows Status: NEW

[pcre-dev] [Bug 2023] CMake error: option called with incorrect number if arguments

https://bugs.exim.org/show_bug.cgi?id=2023 Philip Hazel changed: What|Removed |Added Resolution|--- |FIXED

[pcre-dev] [Bug 2023] CMake error: option called with incorrect number if arguments

https://bugs.exim.org/show_bug.cgi?id=2023 --- Comment #2 from Milan Ziegler --- Thanks for the quick fix. I tested the change for PCRE 8.40 successfully. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 2024] New: MSVC C++ warning due to conversion from ptrdiff_t to int in pcre_exec.c

https://bugs.exim.org/show_bug.cgi?id=2024 Bug ID: 2024 Summary: MSVC C++ warning due to conversion from ptrdiff_t to int in pcre_exec.c Product: PCRE Version: 8.40 Hardware: x86-64 OS: Windows

[pcre-dev] [Bug 2030] New: Exact match mode

https://bugs.exim.org/show_bug.cgi?id=2030 Bug ID: 2030 Summary: Exact match mode Product: PCRE Version: 10.22 (PCRE2) Hardware: x86 OS: Linux Status: NEW Severity: wishlist Priority: medium

[pcre-dev] [Bug 2042] New: Stackoverflow processing pattern "((?:.|\\n)*)"

https://bugs.exim.org/show_bug.cgi?id=2042 Bug ID: 2042 Summary: Stackoverflow processing pattern "((?:.|\\n)*)" Product: PCRE Version: 10.23 (PCRE2) Hardware: x86-64 OS: Windows Status: NEW Severity: bug

[pcre-dev] [Bug 2045] New: heap-based bufffer overflow in regexflip8_or_16 (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2045 Bug ID: 2045 Summary: heap-based bufffer overflow in regexflip8_or_16 (pcretest.c) Product: PCRE Version: 8.40 Hardware: x86-64 OS: Linux Status: NEW

[pcre-dev] [Bug 2043] Invalid memory read in phar (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2043 Petr Pisar changed: What|Removed |Added CC||ppi...@redhat.com --- Comment

[pcre-dev] [Bug 2047] New: infinite loop in pcre_exec.c

https://bugs.exim.org/show_bug.cgi?id=2047 Bug ID: 2047 Summary: infinite loop in pcre_exec.c Product: PCRE Version: 8.40 Hardware: x86 OS: Linux Status: NEW Severity: bug Priority: medium

[pcre-dev] [Bug 2048] New: another infinite loop in pcre_exec.c

https://bugs.exim.org/show_bug.cgi?id=2048 Bug ID: 2048 Summary: another infinite loop in pcre_exec.c Product: PCRE Version: 8.40 Hardware: x86-64 OS: Linux Status: NEW Severity: bug Priority:

[pcre-dev] [Bug 2043] New: Invalid memory read in phar (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2043 Bug ID: 2043 Summary: Invalid memory read in phar (pcretest.c) Product: PCRE Version: 8.40 Hardware: x86-64 OS: Linux Status: NEW Severity: bug

[pcre-dev] [Bug 2044] New: null pointer dereference in main (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2044 Bug ID: 2044 Summary: null pointer dereference in main (pcretest.c) Product: PCRE Version: 8.40 Hardware: x86 OS: Linux Status: NEW Severity: bug

[pcre-dev] [Bug 2042] Stackoverflow processing pattern "((?:.|\\n)*)"

https://bugs.exim.org/show_bug.cgi?id=2042 Philip Hazel changed: What|Removed |Added Resolution|--- |INVALID

[pcre-dev] [Bug 2046] left shift and signed integer overflow in pcretest.c

https://bugs.exim.org/show_bug.cgi?id=2046 --- Comment #1 from Agostino Sarubbo --- Reproducer was missed: https://github.com/asarubbo/poc/blob/master/00197-pcre-leftshift-signintoverflow -- You are receiving this mail because: You are on the CC list for the bug. -- ## List

[pcre-dev] [Bug 2046] New: left shift and signed integer overflow in pcretest.c

https://bugs.exim.org/show_bug.cgi?id=2046 Bug ID: 2046 Summary: left shift and signed integer overflow in pcretest.c Product: PCRE Version: 8.40 Hardware: x86-64 OS: Linux Status: NEW Severity: bug

[pcre-dev] [Bug 2043] Invalid memory read in phar (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2043 --- Comment #3 from Petr Pisar --- And isprint() has undefined behavior on values that cannot be represented in unsigned char although the argument has type int. This is defined by ISO C and POSIX. See similar bug report

[pcre-dev] [Bug 2049] New: infinite loop in pcre_dfa_exec.c

https://bugs.exim.org/show_bug.cgi?id=2049 Bug ID: 2049 Summary: infinite loop in pcre_dfa_exec.c Product: PCRE Version: 8.40 Hardware: x86-64 OS: Linux Status: NEW Severity: bug Priority:

[pcre-dev] [Bug 2050] New: two memory allocation failure in pcretest.c

https://bugs.exim.org/show_bug.cgi?id=2050 Bug ID: 2050 Summary: two memory allocation failure in pcretest.c Product: PCRE Version: 8.40 Hardware: x86-64 OS: Linux Status: NEW Severity: bug

[pcre-dev] [Bug 2050] two memory allocation failure in pcretest.c

https://bugs.exim.org/show_bug.cgi?id=2050 --- Comment #1 from Agostino Sarubbo --- Created attachment 991 --> https://bugs.exim.org/attachment.cgi?id=991=edit stacktrace 2 -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 2043] Invalid memory read in phar (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2043 --- Comment #2 from Petr Pisar --- The crash happens in isprint() function called from pcretest's pchar() via PRINTOK(c) macro on c=449454 value and it can be reduced to: #include #include int main(void) { int a;

[pcre-dev] [Bug 2019] Quantifiers following group comments error

https://bugs.exim.org/show_bug.cgi?id=2019 Philip Hazel changed: What|Removed |Added Resolution|--- |FIXED

[pcre-dev] [Bug 2024] MSVC C++ warning due to conversion from ptrdiff_t to int in pcre_exec.c

https://bugs.exim.org/show_bug.cgi?id=2024 Philip Hazel changed: What|Removed |Added Resolution|--- |FIXED

[pcre-dev] [Bug 2043] Invalid memory read in phar (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2043 Philip Hazel changed: What|Removed |Added Status|NEW |RESOLVED

[pcre-dev] [Bug 2037] A GCC 7 warning about possible buffer overflow in pcregrep when formatting an error message

https://bugs.exim.org/show_bug.cgi?id=2037 Philip Hazel changed: What|Removed |Added Resolution|--- |FIXED

[pcre-dev] [Bug 2051] two null pointer dereference in pcre_exec.c

https://bugs.exim.org/show_bug.cgi?id=2051 --- Comment #2 from Agostino Sarubbo --- (In reply to Philip Hazel from comment #1) > There's a problem here. The URL > > https://github.com/asarubbo/poc/blob/master/00203-pcre-nullptr-pcre_exec > > does not exist. should be fine

[pcre-dev] [Bug 2047] infinite loop in pcre_exec.c

https://bugs.exim.org/show_bug.cgi?id=2047 --- Comment #4 from Agostino Sarubbo --- (In reply to Philip Hazel from comment #1) > Please read the pcrestack man page. This particular example only runs out of > stack on my Linux box if I screw the stack down to 1 MB. This is not a

[pcre-dev] [Bug 2055] stack-based buffer overflow in pcre32_copy_substring (pcre_get.c)

https://bugs.exim.org/show_bug.cgi?id=2055 Philip Hazel changed: What|Removed |Added Status|NEW |RESOLVED

[pcre-dev] [Bug 2056] stack-based buffer overflow in read_capture_name32 (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2056 Philip Hazel changed: What|Removed |Added Status|NEW |RESOLVED

[pcre-dev] [Bug 2057] another stack-based buffer overflow in pcre32_copy_substring (pcre_get.c)

https://bugs.exim.org/show_bug.cgi?id=2057 Philip Hazel changed: What|Removed |Added Status|NEW |RESOLVED

[pcre-dev] [Bug 2055] New: stack-based buffer overflow in pcre32_copy_substring (pcre_get.c)

https://bugs.exim.org/show_bug.cgi?id=2055 Bug ID: 2055 Summary: stack-based buffer overflow in pcre32_copy_substring (pcre_get.c) Product: PCRE Version: 8.40 Hardware: x86-64 OS: Linux Status:

[pcre-dev] [Bug 2051] two null pointer dereference in pcre_exec.c

https://bugs.exim.org/show_bug.cgi?id=2051 Philip Hazel changed: What|Removed |Added Status|NEW |RESOLVED

[pcre-dev] [Bug 2054] New: invalid memory read in _pcre32_xclass (pcre_xclass.c)

https://bugs.exim.org/show_bug.cgi?id=2054 Bug ID: 2054 Summary: invalid memory read in _pcre32_xclass (pcre_xclass.c) Product: PCRE Version: 8.40 Hardware: x86-64 OS: Linux Status: NEW Severity: bug

[pcre-dev] [Bug 2045] heap-based bufffer overflow in regexflip8_or_16 (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2045 --- Comment #4 from Agostino Sarubbo --- it is in the pcretest utility and not in the library. I won't open a new bug about. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 2055] stack-based buffer overflow in pcre32_copy_substring (pcre_get.c)

https://bugs.exim.org/show_bug.cgi?id=2055 --- Comment #1 from Agostino Sarubbo --- Reproducer: https://github.com/asarubbo/poc/blob/master/00207-pcre-stackoverflow-pcre32_copy_substring -- You are receiving this mail because: You are on the CC list for the bug. -- ## List

[pcre-dev] [Bug 2045] heap-based bufffer overflow in regexflip8_or_16 (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2045 --- Comment #3 from Philip Hazel --- I am not particularly worried about ANY issues in pcretest, which is, after all, just a test program, and is also obsolete. If the issue is in the library, I will still look at it. -- You are

[pcre-dev] [Bug 2057] New: another stack-based buffer overflow in pcre32_copy_substring (pcre_get.c)

https://bugs.exim.org/show_bug.cgi?id=2057 Bug ID: 2057 Summary: another stack-based buffer overflow in pcre32_copy_substring (pcre_get.c) Product: PCRE Version: 8.40 Hardware: x86-64 OS: Linux

[pcre-dev] [Bug 2056] New: stack-based buffer overflow in read_capture_name32 (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2056 Bug ID: 2056 Summary: stack-based buffer overflow in read_capture_name32 (pcretest.c) Product: PCRE Version: 8.40 Hardware: x86-64 OS: Linux Status:

[pcre-dev] [Bug 2052] invalid memory read in match (pcre_exec.c)

https://bugs.exim.org/show_bug.cgi?id=2052 Philip Hazel changed: What|Removed |Added Resolution|--- |FIXED

[pcre-dev] [Bug 2057] another stack-based buffer overflow in pcre32_copy_substring (pcre_get.c)

https://bugs.exim.org/show_bug.cgi?id=2057 Brian Martin changed: What|Removed |Added CC|

[pcre-dev] [Bug 2044] null pointer dereference in main (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2044 --- Comment #1 from Philip Hazel --- I'm afraid I'm having a problem with your reproducer. I downloaded it to my Linux box, but it seems to consist of nonsense characters. What is the format? -- You are receiving this mail

[pcre-dev] [Bug 2051] New: two null pointer dereference in pcre_exec.c

https://bugs.exim.org/show_bug.cgi?id=2051 Bug ID: 2051 Summary: two null pointer dereference in pcre_exec.c Product: PCRE Version: N/A Hardware: x86-64 OS: Linux Status: NEW Severity: bug

[pcre-dev] [Bug 2053] another invalid memory read in match (pcre_exec.c)

https://bugs.exim.org/show_bug.cgi?id=2053 --- Comment #1 from Agostino Sarubbo --- Created attachment 994 --> https://bugs.exim.org/attachment.cgi?id=994=edit stacktrace -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 2043] Invalid memory read in phar (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2043 --- Comment #5 from Agostino Sarubbo --- (In reply to Philip Hazel from comment #4) > As you know, I'm doing minimal maintenance for PCRE1 nowadays. I will check pcre2 as well... -- You are receiving this mail because: You are on the

[pcre-dev] [Bug 2044] null pointer dereference in main (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2044 --- Comment #3 from Agostino Sarubbo --- (In reply to Philip Hazel from comment #1) > I'm afraid I'm having a problem with your reproducer. I downloaded it to my > Linux box, but it seems to consist of nonsense characters. What is the >

[pcre-dev] [Bug 2053] New: another invalid memory read in match (pcre_exec.c)

https://bugs.exim.org/show_bug.cgi?id=2053 Bug ID: 2053 Summary: another invalid memory read in match (pcre_exec.c) Product: PCRE Version: 8.40 Hardware: x86-64 OS: Linux Status: NEW Severity: bug

[pcre-dev] [Bug 2052] New: invalid memory read in match (pcre_exec.c)

https://bugs.exim.org/show_bug.cgi?id=2052 Bug ID: 2052 Summary: invalid memory read in match (pcre_exec.c) Product: PCRE Version: 8.40 Hardware: x86-64 OS: Linux Status: NEW Severity: bug

[pcre-dev] [Bug 2047] infinite loop in pcre_exec.c

https://bugs.exim.org/show_bug.cgi?id=2047 --- Comment #2 from Philip Hazel --- *** Bug 2048 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 2048] another infinite loop in pcre_exec.c

https://bugs.exim.org/show_bug.cgi?id=2048 Philip Hazel changed: What|Removed |Added Resolution|--- |DUPLICATE

[pcre-dev] [Bug 2050] two memory allocation failure in pcretest.c

https://bugs.exim.org/show_bug.cgi?id=2050 Philip Hazel changed: What|Removed |Added Resolution|--- |DUPLICATE

[pcre-dev] [Bug 2047] infinite loop in pcre_exec.c

https://bugs.exim.org/show_bug.cgi?id=2047 --- Comment #3 from Philip Hazel --- *** Bug 2049 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 2049] infinite loop in pcre_dfa_exec.c

https://bugs.exim.org/show_bug.cgi?id=2049 Philip Hazel changed: What|Removed |Added Resolution|--- |DUPLICATE

[pcre-dev] [Bug 2047] infinite loop in pcre_exec.c

https://bugs.exim.org/show_bug.cgi?id=2047 Philip Hazel changed: What|Removed |Added Resolution|--- |INVALID

[pcre-dev] [Bug 2044] null pointer dereference in main (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2044 --- Comment #6 from Philip Hazel --- *** Bug 2050 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 2052] invalid memory read in match (pcre_exec.c)

https://bugs.exim.org/show_bug.cgi?id=2052 --- Comment #1 from Philip Hazel --- The reproducer web page does not seem to exist. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 2044] null pointer dereference in main (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2044 --- Comment #5 from Philip Hazel --- *** Bug 2046 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 2044] null pointer dereference in main (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2044 Philip Hazel changed: What|Removed |Added Resolution|--- |FIXED

[pcre-dev] [Bug 2045] heap-based bufffer overflow in regexflip8_or_16 (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2045 Philip Hazel changed: What|Removed |Added Status|NEW |RESOLVED

[pcre-dev] [Bug 2039] Heap Out of bounds read in match() #2

https://bugs.exim.org/show_bug.cgi?id=2039 Philip Hazel changed: What|Removed |Added Status|NEW |RESOLVED

[pcre-dev] [Bug 2041] Heap Out of bounds read in match() #4

https://bugs.exim.org/show_bug.cgi?id=2041 Philip Hazel changed: What|Removed |Added Status|NEW |RESOLVED

[pcre-dev] [Bug 2038] Heap Out of bounds read in match() #1

https://bugs.exim.org/show_bug.cgi?id=2038 Philip Hazel changed: What|Removed |Added Status|NEW |RESOLVED

[pcre-dev] [Bug 2038] Heap Out of bounds read in match() #1

https://bugs.exim.org/show_bug.cgi?id=2038 --- Comment #4 from Philip Hazel --- *** Bug 2041 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 2038] Heap Out of bounds read in match() #1

https://bugs.exim.org/show_bug.cgi?id=2038 --- Comment #2 from Philip Hazel --- *** Bug 2039 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 2038] Heap Out of bounds read in match() #1

https://bugs.exim.org/show_bug.cgi?id=2038 --- Comment #3 from Philip Hazel --- *** Bug 2040 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

[pcre-dev] [Bug 2040] Heap Out of bounds read in match() #3

https://bugs.exim.org/show_bug.cgi?id=2040 Philip Hazel changed: What|Removed |Added Resolution|--- |DUPLICATE

[pcre-dev] [Bug 2039] New: Heap Out of bounds read in match() #2

https://bugs.exim.org/show_bug.cgi?id=2039 Bug ID: 2039 Summary: Heap Out of bounds read in match() #2 Product: PCRE Version: 10.23 (PCRE2) Hardware: x86-64 OS: Linux Status: NEW Severity: bug

[pcre-dev] [Bug 2041] New: Heap Out of bounds read in match() #4

https://bugs.exim.org/show_bug.cgi?id=2041 Bug ID: 2041 Summary: Heap Out of bounds read in match() #4 Product: PCRE Version: 10.23 (PCRE2) Hardware: x86-64 OS: Linux Status: NEW Severity: bug

[pcre-dev] [Bug 2038] New: Heap Out of bounds read in match() #1

https://bugs.exim.org/show_bug.cgi?id=2038 Bug ID: 2038 Summary: Heap Out of bounds read in match() #1 Product: PCRE Version: 10.23 (PCRE2) Hardware: x86-64 OS: Linux Status: NEW Severity: bug

[pcre-dev] [Bug 2038] Heap Out of bounds read in match() #1

https://bugs.exim.org/show_bug.cgi?id=2038 Zoltan Herczeg changed: What|Removed |Added CC||hzmes...@freemail.hu ---

[pcre-dev] [Bug 2042] Stackoverflow processing pattern "((?:.|\\n)*)"

https://bugs.exim.org/show_bug.cgi?id=2042 Raul Bocanegra changed: What|Removed |Added Resolution|INVALID |FIXED ---

[pcre-dev] [Bug 2044] null pointer dereference in main (pcretest.c)

https://bugs.exim.org/show_bug.cgi?id=2044 Petr Pisar changed: What|Removed |Added CC||ppi...@redhat.com --- Comment

[pcre-dev] [Bug 1848] pcregrep outputs duplicate matches

https://bugs.exim.org/show_bug.cgi?id=1848 --- Comment #5 from Eric Hoffman --- Indeed... I think there's missing something though, is to update 'length' in the new code. Otherwise 'length' is invalid when match_pattern() function get called just after taking the goto

[pcre-dev] [Bug 1848] pcregrep outputs duplicate matches

https://bugs.exim.org/show_bug.cgi?id=1848 --- Comment #6 from Philip Hazel --- I do seem to have a problem with this issue, don't I? Thanks again for noticing. I have committed the patch for both PCRE1 and PCRE2 (in the latter case, it will be in the forthcoming 10.23

[pcre-dev] [Bug 2035] Segmentation fault in PHP7.1.1(bundled PCRE8.38)

https://bugs.exim.org/show_bug.cgi?id=2035 Zoltan Herczeg changed: What|Removed |Added Status|NEW |RESOLVED

[pcre-dev] [Bug 1848] pcregrep outputs duplicate matches

https://bugs.exim.org/show_bug.cgi?id=1848 Philip Hazel changed: What|Removed |Added Status|REOPENED|RESOLVED

[pcre-dev] [Bug 1848] pcregrep outputs duplicate matches

https://bugs.exim.org/show_bug.cgi?id=1848 --- Comment #3 from Philip Hazel --- You are absolutely right. Sorry about that. I will fix it in due course, but unfortunately there won't be another release of PCRE1 for a while. However, this is *just* in time for me to fix it

[pcre-dev] [Bug 2037] New: A GCC 7 warning about possible buffer overflow in pcregrep when formatting an error message

https://bugs.exim.org/show_bug.cgi?id=2037 Bug ID: 2037 Summary: A GCC 7 warning about possible buffer overflow in pcregrep when formatting an error message Product: PCRE Version: 8.40 Hardware: x86 URL:

[pcre-dev] [Bug 2035] New: Segmentation fault in PHP7.1.1(bundled PCRE8.38)

https://bugs.exim.org/show_bug.cgi?id=2035 Bug ID: 2035 Summary: Segmentation fault in PHP7.1.1(bundled PCRE8.38) Product: PCRE Version: 8.38 Hardware: x86-64 OS: Linux Status: NEW Severity: security

[pcre-dev] [Bug 1749] PCRE-JITted code should be executed from non-writable memory to obey execmem SELinux restriction

https://bugs.exim.org/show_bug.cgi?id=1749 --- Comment #44 from Petr Pisar --- I confirm the r327 revision works on ARM. I asked a Fedora PowerPC maintainer to give you SSH access to a PPC machine. I CC-ed you in the e-mail. -- You are receiving this mail because: You are

[pcre-dev] [Bug 2019] New: Quantifiers following group comments error

https://bugs.exim.org/show_bug.cgi?id=2019 Bug ID: 2019 Summary: Quantifiers following group comments error Product: PCRE Version: 8.39 Hardware: x86 OS: All Status: NEW Severity: bug Priority:

[pcre-dev] [Bug 2019] Quantifiers following group comments error

https://bugs.exim.org/show_bug.cgi?id=2019 --- Comment #1 from Philip Hazel --- Thank you for the report. Yes, it is indeed a bug. Unfortunately, you have just missed the 8.40 release, which happened earlier this week. I am hoping that 8.40 will be nearly the last, if not

[pcre-dev] [Bug 2062] New: matching Unicode class Pd seems to be hitting additional wrong characters (Po?)

https://bugs.exim.org/show_bug.cgi?id=2062 Bug ID: 2062 Summary: matching Unicode class Pd seems to be hitting additional wrong characters (Po?) Product: PCRE Version: N/A Hardware: All OS: All

[pcre-dev] [Bug 2062] matching Unicode class Pd seems to be hitting additional wrong characters (Po?)

https://bugs.exim.org/show_bug.cgi?id=2062 Petr Pisar changed: What|Removed |Added CC||ppi...@redhat.com --- Comment

[pcre-dev] [Bug 2063] New: [pcre2test] Heap out of bounds read in process_data()

https://bugs.exim.org/show_bug.cgi?id=2063 Bug ID: 2063 Summary: [pcre2test] Heap out of bounds read in process_data() Product: PCRE Version: 10.23 (PCRE2) Hardware: x86-64 OS: Linux Status: NEW Severity:

[pcre-dev] [Bug 2065] New: global buffer overflow write in decode_modifiers (pcre2test.c)

https://bugs.exim.org/show_bug.cgi?id=2065 Bug ID: 2065 Summary: global buffer overflow write in decode_modifiers (pcre2test.c) Product: PCRE Version: 10.22 (PCRE2) Hardware: x86-64 OS: Linux

[pcre-dev] [Bug 1882] New: Different result with PCRE_NO_START_OPTIMISE set

https://bugs.exim.org/show_bug.cgi?id=1882 Bug ID: 1882 Summary: Different result with PCRE_NO_START_OPTIMISE set Product: PCRE Version: 8.39 Hardware: x86 OS: All Status: NEW Severity: bug

[pcre-dev] [Bug 1882] Different result with PCRE_NO_START_OPTIMISE set

https://bugs.exim.org/show_bug.cgi?id=1882 --- Comment #1 from Philip Hazel --- There does indeed seem to be something strange here. I am busy with a large PCRE2 refactoring project at the moment, but I will fix this problem in due course, certainly before the next

<    1   2   3   4   5   6   7   8   9   10   >