CVE-2017-16231
Summary
| CVE | CVE-2017-16231 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2019-03-21 15:59:00 UTC |
| Updated | 2023-11-07 02:40:00 UTC |
| Description | ** DISPUTED ** In 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-recursive call. NOTE: third parties dispute the relevance of this report, noting that there are options that can be used to limit the amount of stack that is used. |
Risk And Classification
Problem Types: CWE-119
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| oss-security - CVE-2017-16231: PCRE 8.41 match() stack overflow; CVE-2017-16232: LibTIFF 4.0.8 memory leaks | MISC | www.openwall.com | Exploit, Mailing List, Third Party Advisory |
| oss-security - Re: CVE-2017-16231: PCRE 8.41 match() stack overflow; CVE-2017-16232: LibTIFF 4.0.8 memory leaks | MISC | www.openwall.com | Exploit, Mailing List, Third Party Advisory |
| oss-security - Re: CVE-2017-16231: PCRE 8.41 match() stack overflow; CVE-2017-16232: LibTIFF 4.0.8 memory leaks | MISC | www.openwall.com | Mailing List, Third Party Advisory |
| PCRE 8.41 Buffer Overflow ≈ Packet Storm | MISC | packetstormsecurity.com | Third Party Advisory, VDB Entry |
| Bug 2047 – infinite loop in pcre_exec.c | CONFIRM | bugs.exim.org | Issue Tracking, Third Party Advisory |
| Malformed Request | MISC | www.securityfocus.com | Third Party Advisory, VDB Entry |
| oss-security - Re: CVE-2017-16231: PCRE 8.41 match() stack overflow; CVE-2017-16232: LibTIFF 4.0.8 memory leaks | MISC | www.openwall.com | Mailing List, Third Party Advisory |
| Full Disclosure: Buffer Overflow in function match() PCRE 8.41 (CVE-2017-16231) | MISC | seclists.org | Mailing List, Third Party Advisory |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.