REDHAT-BUG-384781: Double Free

Published Nov 15, 2007
·
Updated

From pcre changelog, version 6.7:

26. If a subpattern containing a named recursion or subroutine reference such as (?P>B) was quantified, for example (xxx(?P>B)){3}, the calculation of the space required for the compiled pattern went wrong and gave too small a value. Depending on the environment, this could lead to "Failed: internal error: code overflow at offset 49" or "glibc detected double free or corruption" errors.

Acknowledgements:

Red Hat would like to thank Ludwig Nussel for reporting this issue.

Affected Software

1 affected component
PCRE PCRE

Event History

Nov 15, 2007
Data Sourced
03:20 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of REDHAT-BUG-384781?

The severity of REDHAT-BUG-384781 is classified as moderate due to the potential for denial of service through excessive memory use.

2

How do I fix REDHAT-BUG-384781?

To fix REDHAT-BUG-384781, you should upgrade to the latest version of PCRE that addresses this vulnerability.

3

What versions of PCRE are affected by REDHAT-BUG-384781?

REDHAT-BUG-384781 affects older versions of PCRE that include issues with named recursion in quantification.

4

Can REDHAT-BUG-384781 be exploited remotely?

Yes, REDHAT-BUG-384781 can be exploited remotely if an attacker is able to introduce malicious patterns into PCRE.

5

What should I do if I cannot upgrade to fix REDHAT-BUG-384781?

If you cannot upgrade, consider applying temporary mitigations such as restricting input patterns or traffic to vulnerable applications.

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