CVE-2006-7225: Input Validation

Published Nov 15, 2007
·
Updated

From pcre changelog, version 6.7:

18. A valid (though odd) pattern that looked like a POSIX character class but used an invalid character after [ (for example [[,abc,]]) caused pcrecompile() to give the error "Failed: internal error: code overflow" or in some cases to crash with a glibc free() error. This could even happen if the pattern terminated after [[ but there just happened to be a sequence of letters, a binary zero, and a closing ] in the memory that followed.

Acknowledgements:

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

Other sources

Perl-Compatible Regular Expression (PCRE) library before 6.7 allows context-dependent attackers to cause a denial of service (error or crash) via a regular expression that involves a "malformed POSIX character class", as demonstrated via an invalid character after a [[ sequence.

Affected Software

52 affected components
Perl pcre=2.01
Perl pcre=4.0
Perl pcre=5.0
Perl pcre=0.99
Perl pcre=0.94
Perl pcre=4.5
Perl pcre=3.7
Perl pcre=3.6
Perl pcre=3.3
Perl pcre=1.04
Perl pcre=2.06
Perl pcre=3.5
Perl pcre=4.2
Perl pcre=0.98
Perl pcre=1.00
Perl pcre=0.93
Perl pcre=2.04
Perl pcre=6.3
Perl pcre=2.03
Perl pcre=1.02
Perl pcre=1.08
Perl pcre=1.01
Perl pcre=6.1
Perl pcre=0.97
Perl pcre=3.9
Perl pcre=1.05
Perl pcre=6.0
Perl pcre=0.96
Perl pcre=2.08
Perl pcre=1.03
Perl pcre=0.92
Perl pcre=6.5
Perl pcre=6.6
Perl pcre=4.4
Perl pcre=4.1
Perl pcre=0.91
Perl pcre=3.8
Perl pcre=6.2
Perl pcre=3.2
Perl pcre=2.05
Perl pcre=1.07
Perl pcre=1.06
Perl pcre=3.4
Perl pcre=3.0
Perl pcre=0.95
Perl pcre=2.02
Perl pcre=6.4
Perl pcre=3.1
Perl pcre=1.09
Perl pcre=2.07
Perl pcre=4.3
Perl pcre=2.0

Event History

Nov 15, 2007
Data Sourced
via Red Hat·03:14 PM
DescriptionSeverityAffected Software
Dec 3, 2007
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description
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-2006-7225?

CVE-2006-7225 is classified as a critical vulnerability due to its potential to cause application crashes.

2

How does CVE-2006-7225 affect PCRE versions?

CVE-2006-7225 affects multiple versions of PCRE, specifically 0.91 through 6.7.

3

What types of applications are impacted by CVE-2006-7225?

Applications using the affected versions of PCRE for regular expression handling may crash or exhibit errors.

4

How do I fix CVE-2006-7225?

To fix CVE-2006-7225, upgrade to a version of PCRE that is not affected, ideally version 6.8 or greater.

5

What causes the vulnerabilities in CVE-2006-7225?

The vulnerabilities in CVE-2006-7225 are caused by improper handling of invalid character classes in regular expressions.

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