python
- Author: kikadf
- Vulnerable: 2.7.5-2arcturus1
- Unaffected: 2.7.5-2arcturus2
The CGIHTTPServer Python module does not properly handle URL-encoded path separators in URLs.
This is a list of security announcments that have been released for the current stable version of Frugalware
The CGIHTTPServer Python module does not properly handle URL-encoded path separators in URLs.
The CGIHTTPServer Python module does not properly handle URL-encoded path separators in URLs.
Two vulnerabilities have been discovered in dokuwiki. Access control in the media manager was insufficiently restricted and authentication could be bypassed when using Active Directory for LDAP authentication.
Symeon Paraschoudis discovered that PHP incorrectly handled the mkgmtime function. Symeon Paraschoudis discovered that PHP incorrectly handled unserializing objects. Otto Ebeling discovered that PHP incorrectly handled the exif_thumbnail function. Francisco Alonso that PHP incorrectly handled ELF files in the fileinfo extension.
A flaw was found in the way guest provided parameter validation was performed in vmware-vga driver in rectangle handling functionality. bits_per_pixel that are less than 8 could result in accessing non-initialized buffers later in the code due to the expectation that bytes_per_pixel value that is used to initialize these buffers is never zero.
Sogeti found a denial of service flaw in libxml2, a library providing support to read, modify and write XML and HTML files.
HD Moore discovered that Wget contained a path traversal vulnerability when downloading symlinks using FTP.
An out-of-bounds read flaw was found in file’s donote() function in the way the file utility determined the note headers of a elf file.
The ECB Blowfish decryption function assumed that encrypted input would always come in blocks of 12 characters, as specified. However, buggy clients or annoying people may not adhere to that assumption, causing the core to crash while trying to process the invalid base64 input.
The ECB Blowfish decryption function assumed that encrypted input would always come in blocks of 12 characters, as specified. However, buggy clients or annoying people may not adhere to that assumption, causing the core to crash while trying to process the invalid base64 input.