First published: Thu 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 | Affected Version | How to fix |
---|---|---|
PCRE |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-384781 is classified as moderate due to the potential for denial of service through excessive memory use.
To fix REDHAT-BUG-384781, you should upgrade to the latest version of PCRE that addresses this vulnerability.
REDHAT-BUG-384781 affects older versions of PCRE that include issues with named recursion in quantification.
Yes, REDHAT-BUG-384781 can be exploited remotely if an attacker is able to introduce malicious patterns into PCRE.
If you cannot upgrade, consider applying temporary mitigations such as restricting input patterns or traffic to vulnerable applications.