oss-sec mailing list archives
Re: Re: Heap Overflow in PCRE
From: Jakub Wilk <jwilk () jwilk net>
Date: Thu, 3 Dec 2015 13:19:22 +0100
3. The pattern in question for CVE-2015-3210, i.e., the /^(?P=B)((?P=B)(?J:(?P<B>c)(?P<B>a(?P=B)))>WGXCREDITS)/ pattern, doesn't have any instances of something like \1 or \g that are commonly used for a back reference.
(?P=foo) is the Python syntax for backreference, which is supported by PCRE: http://pcre.org/current/doc/html/pcre2syntax.html#SEC20
-- Jakub Wilk
Current thread:
- Re: Heap Overflow in PCRE, (continued)
- Re: Heap Overflow in PCRE Fabian Keil (Nov 24)
- Re: Heap Overflow in PCRE Hanno Böck (Nov 24)
- Re: Heap Overflow in PCRE Fabian Keil (Nov 25)
- Re: Heap Overflow in PCRE Hanno Böck (Nov 24)
- Re: Heap Overflow in PCRE cve-assign (Nov 28)
- Re: Re: Heap Overflow in PCRE Michal Zalewski (Nov 28)
- Re: Heap Overflow in PCRE cve-assign (Nov 29)
- Re: Re: Heap Overflow in PCRE Tomas Hoger (Nov 30)
- Re: Re: Heap Overflow in PCRE Michal Zalewski (Nov 28)
- Re: Heap Overflow in PCRE cve-assign (Dec 01)
- Re: Re: Heap Overflow in PCRE Salvatore Bonaccorso (Dec 02)
- Re: Heap Overflow in PCRE cve-assign (Dec 02)
- Re: Re: Heap Overflow in PCRE Jakub Wilk (Dec 03)
- Re: Heap Overflow in PCRE Fabian Keil (Nov 24)