The match function in pcre_exec.c in PCRE before 8.37 mishandles the
/(?:((abcd))|(((?:(?:(?:(?:abc|(?:abcdef))))b)abcdefghi)abc)|((*ACCEPT)))/
pattern and related patterns involving (*ACCEPT), which allows remote
attackers to obtain sensitive information from process memory or cause a
denial of service (partially initialized memory and application crash) via
a crafted regular expression, as demonstrated by a JavaScript RegExp object
encountered by Konqueror, aka ZDI-CAN-2547.
Author | Note |
---|---|
tyhicks | Issue affects PCRE3 only Marking ‘low’ since it requires PCRE to operate on untrusted regular expressions which is not very likely |
mdeslaur | 794589-information-disclosure.patch in jessie |
vcs.pcre.org/pcre/code/trunk/ChangeLog?view=markup
www.openwall.com/lists/oss-security/2015/08/04/2
www.openwall.com/lists/oss-security/2015/08/04/3
www.openwall.com/lists/oss-security/2015/11/29/1
launchpad.net/bugs/cve/CVE-2015-8382
nvd.nist.gov/vuln/detail/CVE-2015-8382
security-tracker.debian.org/tracker/CVE-2015-8382
ubuntu.com/security/notices/USN-2943-1
www.cve.org/CVERecord?id=CVE-2015-8382