CVE-2006-7230
First published: Thu Nov 15 2007(Updated: )
From pcre changelog, version 7.0: 4. Fixed a major bug that caused incorrect computation of the amount of memory required for a compiled pattern when options that changed within the pattern affected the logic of the preliminary scan that determines the length. The relevant options are -x, and -i in UTF-8 mode. The result was that the computed length was too small. The symptoms of this bug were either the PCRE error "internal error: code overflow" from pcre_compile(), or a glibc crash with a message such as "pcretest: free(): invalid next size (fast)". Examples of patterns that provoked this bug (shown in pcretest format) are: /(?-x: )/x /(?x)(?-x: \s*#\s*)/ /((?i)[\x{c0}])/8 /(?i:[\x{c0}])/8 HOWEVER: Change 17 below makes this fix obsolete as the memory computation is now done differently. Acknowledgements: Red Hat would like to thank Ludwig Nussel for reporting this issue.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| PCRE (Perl Compatible Regular Expressions) | <=6.9 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.pcre.org/changelog.txt
- https://bugzilla.redhat.com/show_bug.cgi?id=384801
- http://security.gentoo.org/glsa/glsa-200711-30.xml
- http://www.redhat.com/support/errata/RHSA-2007-1059.html
- http://www.redhat.com/support/errata/RHSA-2007-1068.html
- http://www.novell.com/linux/security/advisories/2007_62_pcre.html
- http://www.securityfocus.com/bid/26550
- http://secunia.com/advisories/27741
- http://secunia.com/advisories/27773
- http://support.avaya.com/elmodocs2/security/ASA-2007-505.htm
- http://secunia.com/advisories/28041
- http://bugs.gentoo.org/show_bug.cgi?id=198976
- http://security.gentoo.org/glsa/glsa-200801-02.xml
- http://secunia.com/advisories/28406
- http://secunia.com/advisories/28414
- http://security.gentoo.org/glsa/glsa-200801-18.xml
- http://security.gentoo.org/glsa/glsa-200801-19.xml
- http://www.mandriva.com/security/advisories?name=MDVSA-2008:030
- http://lists.opensuse.org/opensuse-security-announce/2008-01/msg00006.html
- http://secunia.com/advisories/28658
- http://secunia.com/advisories/28714
- http://secunia.com/advisories/28720
- http://security.gentoo.org/glsa/glsa-200805-11.xml
- http://secunia.com/advisories/30155
- http://secunia.com/advisories/30219
- http://secunia.com/advisories/30106
- http://www.debian.org/security/2008/dsa-1570
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A10911
- http://rhn.redhat.com/errata/RHSA-2007-1059.html
- http://rhn.redhat.com/errata/RHSA-2007-1068.html
Frequently Asked Questions
What is the severity of CVE-2006-7230?
CVE-2006-7230 has a medium severity rating due to potential memory corruption issues.
How do I fix CVE-2006-7230?
To fix CVE-2006-7230, upgrade to PCRE version 7.0 or later.
Which versions of PCRE are affected by CVE-2006-7230?
CVE-2006-7230 affects PCRE versions up to and including 6.9.
What type of vulnerability is CVE-2006-7230?
CVE-2006-7230 is classified as a memory corruption vulnerability.
Can CVE-2006-7230 lead to code execution?
Yes, CVE-2006-7230 could potentially lead to arbitrary code execution due to improper memory handling.
- collector/redhat-bugzilla
- alias/CVE-2006-7230
- agent/references
- agent/type
- agent/last-modified-date
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- collector/nvd-historical
- vendor/pcre
- product/pcre
- canonical/pcre pcre
- agent/weakness
- agent/severity
- agent/author
- agent/softwarecombine
- agent/tags
- agent/description
- agent/event
- canonical/pcre (perl compatible regular expressions)
- version/pcre (perl compatible regular expressions)/6.9