CVE-2017-7186

Description

References

• securityfocus.com/bid/97030
• access.redhat.com/errata/RHSA-2018:2486
• blogs.gentoo.org/ago/2017/03/14/libpcre-invalid-memory-read-in-match-pcre_exec-c · Patch
• bugs.exim.org/show_bug.cgi · Third Party Advisory
• security.gentoo.org/glsa/201710-09
• security.gentoo.org/glsa/201710-25
• vcs.pcre.org/pcre/code/trunk/pcre_internal.h · Patch
• vcs.pcre.org/pcre/code/trunk/pcre_ucd.c · Patch
• vcs.pcre.org/pcre2/code/trunk/src/pcre2_internal.h · Patch
• vcs.pcre.org/pcre2/code/trunk/src/pcre2_ucd.c · Patch

Weitere Schwachstellen in pcre

• CVE-2020-14155MITTEL 5.3libpcre in PCRE before 8.44 allows an integer overflow via a large number after a (?C substring.
• CVE-2019-20838HOCH 7.5libpcre in PCRE before 8.43 allows a subject buffer over-read in JIT when UTF is disabled, and \X or \R has more than one fixed quantifier, …
• CVE-2015-2326MITTEL 5.5The pcre_compile2 function in PCRE before 8.37 allows context-dependent attackers to compile incorrect code and cause a denial of service (o…
• CVE-2015-2325HOCH 7.8The compile_branch function in PCRE before 8.37 allows context-dependent attackers to compile incorrect code, cause a denial of service (out…
• CVE-2017-16231MITTEL 5.5In PCRE 8.41, after compiling, a pcretest load test PoC produces a crash overflow in the function match() in pcre_exec.c because of a self-r…