Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security Exploits-HackingTools
[Top] [All Lists]

[NEWS] GIMP XCF Parsing xcf_load_vector() Function Overflow

Subject: [NEWS] GIMP XCF Parsing xcf_load_vector() Function Overflow
Date: 25 Jul 2006 13:42:43 +0200
The following security advisory is sent to the securiteam mailing list, and can 
be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion

The SecuriTeam alerts list - Free, Accurate, Independent.

Get your security news from a reliable source.
http://www.securiteam.com/mailinglist.html 

- - - - - - - - -



  GIMP XCF Parsing xcf_load_vector() Function Overflow
------------------------------------------------------------------------


SUMMARY

Buffer overflow in the xcf_load_vector function in app/xcf/xcf-load.c for 
GIMP before 2.2.12 allows user-complicit attackers to cause a denial of 
service (crash) and possibly execute arbitrary code via an XCF file with a 
large num_axes value in the VECTORS property.

DETAILS

Vulnerable Systems:
 * GIMP version 2.2.11

Immune Systems:
 * GIMP version 2.2.12

The problem is in the function xcf_load_vector() in app/xcf/xcf-load.c of 
the source tree. For each "stroke" being read, the code reads an uint32 
from the XCF file into the variable num_axes, and then for each control 
proint of the stroke reads num_axes floats from the file into the 
stack-allocated array coords whose size is hard-coded as 6.

A malicious XCF file creator could write a large number into the num_axes 
position and trick the XCF reader into overwriting part of the stack with 
raw data read from the file. On little-endian systems, the function 
xcf_read_float() that actually reads the floats does a byte-order 
conversion on the data it reads but does not do any special float 
processing, so an attacker has direct control of the data written to the 
stack.

The attack is in the VECTORS property of an XCF file which pure XCF 
_viewers_ (e.g. imagemagick or xcftools) normally skip without parsing. 
Thus an attack file can easily be written such that the image will display 
correctly with no symptoms at all in a viewer application.


ADDITIONAL INFORMATION

The information has been provided by Justin M. Forbes.
The original article can be found at:  
<https://issues.rpath.com/browse/RPL-522> 
https://issues.rpath.com/browse/RPL-522



======================================== 


This bulletin is sent to members of the SecuriTeam mailing list. 
To unsubscribe from the list, send mail with an empty subject line and body to: 
list-unsubscribe@securiteam.com 
In order to subscribe to the mailing list, simply forward this email to: 
list-subscribe@securiteam.com 


==================== 
==================== 

DISCLAIMER: 
The information in this bulletin is provided "AS IS" without warranty of any 
kind. 
In no event shall we be liable for any damages whatsoever including direct, 
indirect, incidental, consequential, loss of business profits or special 
damages. 




<Prev in Thread] Current Thread [Next in Thread>
  • [NEWS] GIMP XCF Parsing xcf_load_vector() Function Overflow, SecuriTeam <=