S-201: PCRE3 Vulnerability


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) S-201: PCRE3 Vulnerability
# 1  
Old 02-25-2008
S-201: PCRE3 Vulnerability

It was discovered that spsecially crafted regular expressions involving codeprints greater than 255 could cause a buffer overflow in the PCRE library. The risk is LOW.


More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
PCRE_GET_STRINGTABLE_ENTRIES(3) 			     Library Functions Manual				   PCRE_GET_STRINGTABLE_ENTRIES(3)

NAME
PCRE - Perl-compatible regular expressions SYNOPSIS
#include <pcre.h> int pcre_get_stringtable_entries(const pcre *code, const char *name, char **first, char **last); DESCRIPTION
This convenience function finds, for a compiled pattern, the first and last entries for a given name in the table that translates capturing parenthesis names into numbers. When names are required to be unique (PCRE_DUPNAMES is not set), it is usually easier to use pcre_get_stringnumber() instead. code Compiled regular expression name Name whose entries required first Where to return a pointer to the first entry last Where to return a pointer to the last entry The yield of the function is the length of each entry, or PCRE_ERROR_NOSUBSTRING if none are found. There is a complete description of the PCRE native API, including the format of the table entries, in the pcreapi page, and a description of the POSIX API in the pcreposix page. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +--------------------+-----------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +--------------------+-----------------+ |Availability | SUNWpcre | +--------------------+-----------------+ |Interface Stability | Uncommitted | +--------------------+-----------------+ NOTES
Source for PCRE is available on http://opensolaris.org. PCRE_GET_STRINGTABLE_ENTRIES(3)