Bug#858679: Issue CVE-2017-7246 persist on current upstrem r16892d

On Sun, 26 Mar 2017, Salvatore Bonaccorso wrote: > I tried to follow the status for CVE-2017-7246 (#858679), and it looks > they fail still on "current" revision from upstrema VCS. I believe this is the same bug in pcretest that I have just fixed for CVE-2017-7245. Regards, Philip -- Philip Ha

Bug#858678: Issue CVE-2017-7245 persist on current upstream r1689

On Sun, 26 Mar 2017, Salvatore Bonaccorso wrote: > I tried to follow the status for CVE-2017-7245 (#858678), and it looks > they fail still on "current" revision from upstrema VCS. I believe I have fixed this at r1691. It was a one-character typo in pcretest, causing an incorrect buffer length to

Bug#858678: Issue CVE-2017-7245 persist on current upstream r1689

On Sun, 26 Mar 2017, Salvatore Bonaccorso wrote: > Sure, apolgies if this was too terse. So the CVE-2017-7245 issue, some > references are here: > > https://security-tracker.debian.org/tracker/CVE-2017-7245 > > the reporter blog is at > https://blogs.gentoo.org/ago/2017/03/20/libpcre-two-stack-b

Bug#858678: Issue CVE-2017-7245 persist on current upstream r1689

On Sun, 26 Mar 2017, Salvatore Bonaccorso wrote: > I tried to follow the status for CVE-2017-7245 (#858678), and it looks > they fail still on "current" revision from upstrema VCS. > > I'm on r1689 ("Fix DFA match handling of possessive repeated character > class (Bugzilla 2086).") and compiling