Solaris is a UNIX operating system developed by Sun Microsystems. More information can be found at the following URL.
Local exploitation of an integer signedness error in Sun Microsystem's Solaris could allow attackers to disclose sensitive information from memory.
The FIFO FS (First In First Out File System) is a service provided by the kernel that is commonly used for IPC (InterProcess Communication). A FIFO is represented as a node in the file system, and is similar to the concept of named pipes in Windows.
The vulnerability exists in the kernel ioctl() handler for FIFOs. The I_PEEK ioctl is used to peek at a number of bytes contained in the FIFO without actually removing them from the queue. One of the arguments to this command, which represents the number of bytes to peek, is a signed integer value. Since this parameter is not properly validated, a negative value can cause large amounts of kernel memory contents to be disclosed.
Exploitation allows an attacker to view potentially sensitive information belonging to the kernel or other users. For example, the root password hash or encryption keys might be disclosed.
iDefense has confirmed the existence of this vulnerability in Solaris 10 on x86 and SPARC. It is suspected that earlier versions are also affected.
iDefense is not aware of any workaround for this issue.
Sun has addressed this vulnerability by releasing patches. For more information, consult Sun Alert 103061 at the following URL.
A Mitre Corp. Common Vulnerabilities and Exposures (CVE) number has not been assigned yet.
02/13/2007 Initial vendor notification
02/15/2007 Initial vendor response
10/02/2007 Coordinated public disclosure
The discoverer of this vulnerability wishes to remain anonymous.
Get paid for vulnerability research
Free tools, research and upcoming events
Copyright © 2007 Verisign, Inc.
Permission is granted for the redistribution of this alert electronically. It may not be edited in any way without the express written consent of iDefense. If you wish to reprint the whole or any part of this alert in any other medium other than electronically, please e-mail customer service for permission.
Disclaimer: The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.