Login or Register to Ask a Question and Join Our Community


Security Advisories (RSS)

Mandriva: Subject: [Security Announce] [ MDVSA-2008:204 ] blender

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums Cybersecurity Security Advisories (RSS) Mandriva: Subject: [Security Announce] [ MDVSA-2008:204 ] blender
# 1  
Old 09-24-2008
Mandriva: Subject: [Security Announce] [ MDVSA-2008:204 ] blender
LinuxSecurity.com: Stefan Cornelius of Secunia Research reported a boundary error when Blender processed RGBE images which could be used to execute arbitrary code with the privileges of the user running Blender if a specially crafted .hdr or .blend file were opened(CVE-2008-1102). As well, multiple vulnerabilities involving insecure usage of temporary files had also been reported (CVE-2008-1103). The updated packages have been patched to prevent these issues.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT DEBIAN

imager::security

Imager::Security(3pm)					User Contributed Perl Documentation				     Imager::Security(3pm)

NAME

       Imager::Security - brief notes on security and image processing

SYNOPSIS

	 # keep abreast of security updates
	 apt-get update && apt-get upgrade
	 yum upgrade
	 pkgin update && pkgin upgrade
	 # or local equivalent

	 # limit memory use
	 use Imager;
	 # only images that use up to 10MB
	 Imager->set_file_limits(bytes => 10_000_000);

DESCRIPTION

       There's two basic security considerations when dealing with images from an unknown source:

       o   keeping your libraries up to date

       o   limiting the amount of memory used to store images

   Keeping libraries up to date
       Image file format libraries such as "libpng" or "libtiff" have relatively frequent security updates, keeping your libraries up to date is
       basic security.

       If you're using user supplied fonts, you will need to keep your font libraries up to date too.

   Limiting memory used
       With compression, and especially with pointer formats like TIFF, it's possible to store very large images in a relatively small file.

       If you're receiving image data from an untrusted source you should limit the amount of memory that Imager can allocate for a read in image
       file using the "set_file_limits()" method.

	 Imager->set_file_limits(bytes => 10_000_000);

       You may also want to limit the maximum width and height of images read from files:

	 Imager->set_file_limits(width => 10_000, height => 10_000,
				 bytes => 10_000_000);

       This has no effect on images created without a file:

	 # succeeds
	 my $image = Imager->new(xsize => 10_001, ysize => 10_001);

       You can reset to the defaults with:

	 Imager->set_file_limits(reset => 1);

AUTHOR

       Tony Cook <tonyc@cpan.org>

perl v5.14.2							    2012-06-04						     Imager::Security(3pm)