CVE-2017-16231: Buffer Overflow

Published Mar 17, 2019
·
Updated

DISPUTED In PCRE 8.41, after compiling, a pcretest load test PoC produces a crash overflow in the function match() in pcreexec.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.

Affected Software

1 affected component
PCRE PCRE=8.41

Event History

Mar 17, 2019
CVE Published
via MITRE·04:24 PM
Data Sourced
via MITRE·04:24 PM
Description
Mar 21, 2019
Disputed
03:59 PM
Data Sourced
via NVD·03:59 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2017-16231?

The severity of CVE-2017-16231 is medium with a severity value of 5.5.

2

What is the affected software of CVE-2017-16231?

The affected software of CVE-2017-16231 is PCRE version 8.41.

3

How does CVE-2017-16231 occur?

CVE-2017-16231 occurs due to a crash overflow in the function match() in pcre_exec.c, caused by a self-recursive call.

4

Is CVE-2017-16231 disputed?

Yes, CVE-2017-16231 is disputed by third parties who argue that there are options available to limit the impact.

5

Are there any references available for CVE-2017-16231?

Yes, there are references available for CVE-2017-16231 which include: http://packetstormsecurity.com/files/150897/PCRE-8.41-Buffer-Overflow.html, http://seclists.org/fulldisclosure/2018/Dec/33, and http://www.openwall.com/lists/oss-security/2017/11/01/11.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203