Gentoo: PECL APC Buffer Overflow


 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) Gentoo: PECL APC Buffer Overflow
# 1  
Old 04-09-2008
Gentoo: PECL APC Buffer Overflow

LinuxSecurity.com: A buffer overflow vulnerability in PECL APC might allow for the remote execution of arbitrary code.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. AIX

nim mksysb buffer overflow error

Hi, I am trying to backup a system ("client") through a slow network using "nim mksysb" on a nim server ("master") The backup starts, but doesn't success. Thanks if you can help me to resolve this problem : Creating information file (/image.data) for rootvg... Creating list of files to... (2 Replies)
Discussion started by: astjen
2 Replies

2. UNIX for Dummies Questions & Answers

Printer buffer overflow

I have an Oki-Page 14ex with 4MB of RAM. Whenever I print large documents or a several small documents, I get a buffer overflow. Can anyone help? Thanks. If there is any additional information you need, please feel free to ask. Tim (3 Replies)
Discussion started by: AltatemTC
3 Replies
Login or Register to Ask a Question
Paranoid::Log::Buffer(3pm)				User Contributed Perl Documentation				Paranoid::Log::Buffer(3pm)

NAME
Paranoid::Log::Buffer - Log Buffer Functions VERSION
$Id: Buffer.pm,v 0.83 2010/06/03 19:03:46 acorliss Exp $ SYNOPSIS
use Paranoid::Log; enableFacility('events', 'buffer', 'debug', '+'); enableFacility('more-events', 'buffer', 'debug', '+', 100); @messages = Paranoid::Log::Buffer::dump($name); DESCRIPTION
This module implements named buffers to be used for logging purposes. Each buffer is of a concrete size (definable by the developer) with a max message length of 2KB. Each message is stored with a timestamp. Once the buffer hits the maximun number of entries it begins deleting the oldest messages as the new messages come in. Buffers are created automatically on the fly, and messages trimmed before being stored. With the exception of the dump function this module is not meant to be used directly. Paranoid::Log should be your exclusive interface for logging. When enabling a buffer facility with Paranoid::Log you can add one integral argument to the call. That number defines the size of the log buffer in terms of number of entries allowed. NOTE: Buffers are maintained within process memory. If you fork a process from a parent with a log buffer each copy will maintain its own entries. SUBROUTINES
/METHODS NOTE: Given that this module is not intended to be used directly nothing is exported. init log remove Paranoid::Log::Buffer::dump @entries = Paranoid::Log::Buffer::dump($name); This dumps all current entries in the named buffer. Each entry is an array reference to a two-element array. The first element is the timestamp of the message (in UNIX epoch seconds), the second the actual message itself. DEPENDENCIES
o Paranoid::Debug SEE ALSO
o Paranoid::Log BUGS AND LIMITATIONS
AUTHOR
Arthur Corliss (corliss@digitalmages.com) LICENSE AND COPYRIGHT
This software is licensed under the same terms as Perl, itself. Please see http://dev.perl.org/licenses/ for more information. (c) 2005, Arthur Corliss (corliss@digitalmages.com) perl v5.14.2 2010-06-03 Paranoid::Log::Buffer(3pm)