From ${URL} : PCRE library is prone to a vulnerability which leads to Heap Overflow. During the compilation of a malformed regular expression, more data is written on the malloced block than the expected size output by compile_regex. Carefully crafted my lead to code execution in the context of affected applications. Reference: https://bugs.exim.org/show_bug.cgi?id=1767 @maintainer(s): after the bump, in case we need to stabilize the package, please let us know if it is ready for the stabilization or not.
*** Bug 573842 has been marked as a duplicate of this bug. ***
added upstream patches; should be fined to stable: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cee01d4f06b3984b8211bd3c27358f7d18cf90fb
CVE-2016-1283 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1283): The pcre_compile2 function in pcre_compile.c in PCRE 8.38 mishandles the /((?:F?+(?:^(?(R)a+\"){99}-))(?J)(?'R'(?'R'<((?'RR'(?'R'\){97)?J)?J)(?'R'(?'R'\){99|(:(?|(?'R')(\k'R')|((?'R')))H'R'R)(H'R))))))/ pattern and related patterns with named subgroups, which allows remote attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror.
Added to existing GLSA.
This issue was resolved and addressed in GLSA 201607-02 at https://security.gentoo.org/glsa/201607-02 by GLSA coordinator Aaron Bauman (b-man).
