/[pcre]/code/trunk/ChangeLog

Diff of /code/trunk/ChangeLog

Parent Directory | Revision Log | View Patch Patch

-revision 1534 by ph10,
Tue Mar 24 10:33:21 2015 UTC
+revision 1614 by ph10,
Sun Nov 29 17:38:25 2015 UTC
 Line 1
  ChangeLog for PCRE
  ------------------
- Version 8.37 xx-xxx-2015
+ Note that the PCRE 8.xx series (PCRE1) is now in a bugfix-only state. All
- ------------------------
+ development is happening in the PCRE2 10.xx series.
+ Version 8.39 xx-xxxxxx-201x
+ ---------------------------
+.  If PCRE_AUTO_CALLOUT was set on a pattern that had a (?# comment between
+     an item and its qualifier (for example, A(?#comment)?B) pcre_compile()
+     misbehaved. This bug was found by the LLVM fuzzer.
+.  Similar to the above, if an isolated \E was present between an item and its
+     qualifier when PCRE_AUTO_CALLOUT was set, pcre_compile() misbehaved. This
+     bug was found by the LLVM fuzzer.
+.  Further to 8.38/46, negated classes such as [^[:^ascii:]\d] were also not
+     working correctly in UCP mode.
+.  The POSIX wrapper function regexec() crashed if the option REG_STARTEND
+     was set when the pmatch argument was NULL. It now returns REG_INVARG.
+ Version 8.38 23-November-2015
+ -----------------------------
+.  If a group that contained a recursive back reference also contained a
+     forward reference subroutine call followed by a non-forward-reference
+     subroutine call, for example /.((?2)(?R)\1)()/, pcre2_compile() failed to
+     compile correct code, leading to undefined behaviour or an internally
+     detected error. This bug was discovered by the LLVM fuzzer.
+.  Quantification of certain items (e.g. atomic back references) could cause
+     incorrect code to be compiled when recursive forward references were
+     involved. For example, in this pattern: /(?1)()((((((\1++))\x85)+)|))/.
+     This bug was discovered by the LLVM fuzzer.
+.  A repeated conditional group whose condition was a reference by name caused
+     a buffer overflow if there was more than one group with the given name.
+     This bug was discovered by the LLVM fuzzer.
+.  A recursive back reference by name within a group that had the same name as
+     another group caused a buffer overflow. For example:
+     /(?J)(?'d'(?'d'\g{d}))/. This bug was discovered by the LLVM fuzzer.
+.  A forward reference by name to a group whose number is the same as the
+     current group, for example in this pattern: /(?|(\k'Pm')|(?'Pm'))/, caused
+     a buffer overflow at compile time. This bug was discovered by the LLVM
+     fuzzer.
+.  A lookbehind assertion within a set of mutually recursive subpatterns could
+     provoke a buffer overflow. This bug was discovered by the LLVM fuzzer.
+.  Another buffer overflow bug involved duplicate named groups with a
+     reference between their definition, with a group that reset capture
+     numbers, for example: /(?J:(?|(?'R')(\k'R')|((?'R'))))/. This has been
+     fixed by always allowing for more memory, even if not needed. (A proper fix
+     is implemented in PCRE2, but it involves more refactoring.)
+.  There was no check for integer overflow in subroutine calls such as (?123).
+.  The table entry for \l in EBCDIC environments was incorrect, leading to its
+     being treated as a literal 'l' instead of causing an error.
+. There was a buffer overflow if pcre_exec() was called with an ovector of
+     size 1. This bug was found by american fuzzy lop.
+. If a non-capturing group containing a conditional group that could match
+     an empty string was repeated, it was not identified as matching an empty
+     string itself. For example: /^(?:(?(1)x|)+)+$()/.
+. In an EBCDIC environment, pcretest was mishandling the escape sequences
+     \a and \e in test subject lines.
+. In an EBCDIC environment, \a in a pattern was converted to the ASCII
+     instead of the EBCDIC value.
+. The handling of \c in an EBCDIC environment has been revised so that it is
+     now compatible with the specification in Perl's perlebcdic page.
+. The EBCDIC character 0x41 is a non-breaking space, equivalent to 0xa0 in
+     ASCII/Unicode. This has now been added to the list of characters that are
+     recognized as white space in EBCDIC.
+. When PCRE was compiled without UCP support, the use of \p and \P gave an
+     error (correctly) when used outside a class, but did not give an error
+     within a class.
+. \h within a class was incorrectly compiled in EBCDIC environments.
+. A pattern with an unmatched closing parenthesis that contained a backward
+     assertion which itself contained a forward reference caused buffer
+     overflow. And example pattern is: /(?=di(?<=(?1))|(?=(.))))/.
+. JIT should return with error when the compiled pattern requires more stack
+     space than the maximum.
+. A possessively repeated conditional group that could match an empty string,
+     for example, /(?(R))*+/, was incorrectly compiled.
+. Fix infinite recursion in the JIT compiler when certain patterns such as
+     /(?:|a|){100}x/ are analysed.
+. Some patterns with character classes involving [: and \\ were incorrectly
+     compiled and could cause reading from uninitialized memory or an incorrect
+     error diagnosis.
+. Pathological patterns containing many nested occurrences of [: caused
+     pcre_compile() to run for a very long time.
+. A conditional group with only one branch has an implicit empty alternative
+     branch and must therefore be treated as potentially matching an empty
+     string.
+. If (?R was followed by - or + incorrect behaviour happened instead of a
+     diagnostic.
+. Arrange to give up on finding the minimum matching length for overly
+     complex patterns.
+. Similar to (4) above: in a pattern with duplicated named groups and an
+     occurrence of (?| it is possible for an apparently non-recursive back
+     reference to become recursive if a later named group with the relevant
+     number is encountered. This could lead to a buffer overflow. Wen Guanxing
+     from Venustech ADLAB discovered this bug.
+. If pcregrep was given the -q option with -c or -l, or when handling a
+     binary file, it incorrectly wrote output to stdout.
+. The JIT compiler did not restore the control verb head in case of *THEN
+     control verbs. This issue was found by Karl Skomski with a custom LLVM
+     fuzzer.
+. Error messages for syntax errors following \g and \k were giving inaccurate
+     offsets in the pattern.
+. Added a check for integer overflow in conditions (?(<digits>) and
+     (?(R<digits>). This omission was discovered by Karl Skomski with the LLVM
+     fuzzer.
+. Handling recursive references such as (?2) when the reference is to a group
+     later in the pattern uses code that is very hacked about and error-prone.
+     It has been re-written for PCRE2. Here in PCRE1, a check has been added to
+     give an internal error if it is obvious that compiling has gone wrong.
+. The JIT compiler should not check repeats after a {0,1} repeat byte code.
+     This issue was found by Karl Skomski with a custom LLVM fuzzer.
+. The JIT compiler should restore the control chain for empty possessive
+     repeats. This issue was found by Karl Skomski with a custom LLVM fuzzer.
+. Match limit check added to JIT recursion. This issue was found by Karl
+     Skomski with a custom LLVM fuzzer.
+. Yet another case similar to 27 above has been circumvented by an
+     unconditional allocation of extra memory. This issue is fixed "properly" in
+     PCRE2 by refactoring the way references are handled. Wen Guanxing
+     from Venustech ADLAB discovered this bug.
+. Fix two assertion fails in JIT. These issues were found by Karl Skomski
+     with a custom LLVM fuzzer.
+. Fixed a corner case of range optimization in JIT.
+. An incorrect error "overran compiling workspace" was given if there were
+     exactly enough group forward references such that the last one extended
+     into the workspace safety margin. The next one would have expanded the
+     workspace. The test for overflow was not including the safety margin.
+. A match limit issue is fixed in JIT which was found by Karl Skomski
+     with a custom LLVM fuzzer.
+. Remove the use of /dev/null in testdata/testinput2, because it doesn't
+     work under Windows. (Why has it taken so long for anyone to notice?)
+. In a character class such as [\W\p{Any}] where both a negative-type escape
+     ("not a word character") and a property escape were present, the property
+     escape was being ignored.
+. Fix crash caused by very long (*MARK) or (*THEN) names.
+. A sequence such as [[:punct:]b] that is, a POSIX character class followed
+     by a single ASCII character in a class item, was incorrectly compiled in
+     UCP mode. The POSIX class got lost, but only if the single character
+     followed it.
+. [:punct:] in UCP mode was matching some characters in the range 128-255
+     that should not have been matched.
+. If [:^ascii:] or [:^xdigit:] or [:^cntrl:] are present in a non-negated
+     class, all characters with code points greater than 255 are in the class.
+     When a Unicode property was also in the class (if PCRE_UCP is set, escapes
+     such as \w are turned into Unicode properties), wide characters were not
+     correctly handled, and could fail to match.
+ Version 8.37 28-April-2015
+ --------------------------
 .  When an (*ACCEPT) is triggered inside capturing parentheses, it arranges
      for those parentheses to be closed with whatever has been captured so far.
-Line 41 
 Version 8.37 xx-xxx-2015
+Line 235 
 Version 8.37 xx-xxx-2015
     was no other kind of back reference (a situation which is probably quite
     rare). The effect of the bug was that the condition was always treated as
     FALSE when the capture could not be consulted, leading to a incorrect
-    behaviour by pcre2_match(). This bug has been fixed.
+    behaviour by pcre_exec(). This bug has been fixed.
 . A reference to a duplicated named group (either a back reference or a test
     for being set in a conditional) that occurred in a part of the pattern where
-Line 65 
 Version 8.37 xx-xxx-2015
+Line 259 
 Version 8.37 xx-xxx-2015
      failed to allow the zero-repeat case if pcre2_exec() was called with an
      ovector too small to capture the group.
 . Fixed two bugs in pcretest that were discovered by fuzzing and reported by
      Red Hat Product Security:
      (a) A crash if /K and /F were both set with the option to save the compiled
-Line 74 
 Version 8.37 xx-xxx-2015
+Line 268 
 Version 8.37 xx-xxx-2015
      (b) Another crash if the option to print captured substrings in a callout
      was combined with setting a null ovector, for example \O\C+ as a subject
      string.
 . A pattern such as "((?2){0,1999}())?", which has a group containing a
      forward reference repeated a large (but limited) number of times within a
      repeated outer group that has a zero minimum quantifier, caused incorrect
      code to be compiled, leading to the error "internal error:
      previously-checked referenced subpattern not found" when an incorrect
      memory address was read. This bug was reported as "heap overflow",
      discovered by Kai Lu of Fortinet's FortiGuard Labs and given the CVE number
      CVE-2015-2325.
 . A pattern such as "((?+1)(\1))/" containing a forward reference subroutine
      call within a group that also contained a recursive back reference caused
      incorrect code to be compiled. This bug was reported as "heap overflow",
      discovered by Kai Lu of Fortinet's FortiGuard Labs, and given the CVE
      number CVE-2015-2326.
 . Computing the size of the JIT read-only data in advance has been a source
-Line 102 
 Version 8.37 xx-xxx-2015
+Line 296 
 Version 8.37 xx-xxx-2015
 . Fix JIT compilation of conditional blocks, which assertion
      is converted to (*FAIL). E.g: /(?(?!))/.
 . The pattern /(?(?!)^)/ caused references to random memory. This bug was
      discovered by the LLVM fuzzer.
-Line 111 
 Version 8.37 xx-xxx-2015
+Line 305 
 Version 8.37 xx-xxx-2015
      pcre2_match() it worked by luck; in pcre2_dfa_match() it gave an incorrect
      error about an unsupported item.
+. For some types of pattern, for example /Z*(|d*){216}/, the auto-
+     possessification code could take exponential time to complete. A recursion
+     depth limit of 1000 has been imposed to limit the resources used by this
+     optimization.
+. A pattern such as /(*UTF)[\S\V\H]/, which contains a negated special class
+     such as \S in non-UCP mode, explicit wide characters (> 255) can be ignored
+     because \S ensures they are all in the class. The code for doing this was
+     interacting badly with the code for computing the amount of space needed to
+     compile the pattern, leading to a buffer overflow. This bug was discovered
+     by the LLVM fuzzer.
+. A pattern such as /((?2)+)((?1))/ which has mutual recursion nested inside
+     other kinds of group caused stack overflow at compile time. This bug was
+     discovered by the LLVM fuzzer.
+. A pattern such as /(?1)(?#?'){8}(a)/ which had a parenthesized comment
+     between a subroutine call and its quantifier was incorrectly compiled,
+     leading to buffer overflow or other errors. This bug was discovered by the
+     LLVM fuzzer.
+. The illegal pattern /(?(?<E>.*!.*)?)/ was not being diagnosed as missing an
+     assertion after (?(. The code was failing to check the character after
+     (?(?< for the ! or = that would indicate a lookbehind assertion. This bug
+     was discovered by the LLVM fuzzer.
+. A pattern such as /X((?2)()*+){2}+/ which has a possessive quantifier with
+     a fixed maximum following a group that contains a subroutine reference was
+     incorrectly compiled and could trigger buffer overflow. This bug was
+     discovered by the LLVM fuzzer.
+. A mutual recursion within a lookbehind assertion such as (?<=((?2))((?1)))
+     caused a stack overflow instead of the diagnosis of a non-fixed length
+     lookbehind assertion. This bug was discovered by the LLVM fuzzer.
+. The use of \K in a positive lookbehind assertion in a non-anchored pattern
+     (e.g. /(?<=\Ka)/) could make pcregrep loop.
+. There was a similar problem to 36 in pcretest for global matches.
+. If a greedy quantified \X was preceded by \C in UTF mode (e.g. \C\X*),
+     and a subsequent item in the pattern caused a non-match, backtracking over
+     the repeated \X did not stop, but carried on past the start of the subject,
+     causing reference to random memory and/or a segfault. There were also some
+     other cases where backtracking after \C could crash. This set of bugs was
+     discovered by the LLVM fuzzer.
+. The function for finding the minimum length of a matching string could take
+     a very long time if mutual recursion was present many times in a pattern,
+     for example, /((?2){73}(?2))((?1))/. A better mutual recursion detection
+     method has been implemented. This infelicity was discovered by the LLVM
+     fuzzer.
+. Static linking against the PCRE library using the pkg-config module was
+     failing on missing pthread symbols.
  Version 8.36 26-September-2014
  ------------------------------

 Legend:



Removed from v.1534
 


changed lines


 
Added in v.1614
 Legend:



Removed from v.1534
 


changed lines


 
Added in v.1614
-Removed from v.1534
+Added in v.1614

	ViewVC Help
Powered by ViewVC 1.1.5