Solaris Sun Remote Services Net Connect 'srsexec' Utility Lets Local Users View Arbitrary Files
SecurityTracker Alert ID: 1018046|
SecurityTracker URL: http://securitytracker.com/id/1018046
(Links to External Site)
Updated: May 12 2008|
Original Entry Date: May 10 2007
Disclosure of system information, Disclosure of user information|
Fix Available: Yes Vendor Confirmed: Yes |
Version(s): 8, 9, 10|
A vulnerability was reported in the Sun Remote Services (SRS) Net Connect software for Solaris. A local user can view arbitrary files on the target system.|
A local user can invoke the 'srsexec' utility with the '-v' and '-d' switches to view portions of arbitrary files on the target system.
The vendor was notified on November 7, 2006.
iDefense reported this vulnerability.
A local user view portions of arbitrary files on the target system.|
The vendor has issued the following fixes.|
* SRS Net Connect Software 3.2.3 (for Solaris 8, 9 and 10) with patch 125713-01 or later
* SRS Net Connect Software 3.2.4 (for Solaris 8, 9 and 10) with patch 123870-02 or later
The Sun advisory is available at:
Vendor URL: sunsolve.sun.com/search/document.do?assetkey=1-26-102891-1 (Links to External Site)
Access control error|
Source Message Contents
Subject: iDefense Security Advisory 05.10.07: Sun Microsystems Solaris SRS|
Sun Microsystems Solaris SRS Proxy Core srsexec Arbitrary File Read
iDefense Security Advisory 05.10.07
May 10, 2007
The srsexec utility is part of the SRS Proxy Core package that is
available with Solaris 10. It is installed setuid root by default. For
more information about this software, visit the following URL.
Local exploitation of a design error vulnerability in the srsexec binary
optionally included in Sun Microsystems Inc., Solaris 10 allows
attackers to gain access to sensitive information, such as the root
The vulnerability specifically exists because of a failure to drop
permissions or check the permissions on the file specified for the
target file. If a user specified verify only mode (-v) as well as debug
mode (-d), and specified a protected file such as /etc/shadow, srsexec
will display the first line of /etc/shadow in the debug messages. The
following demonstrates a sample exploitation session:
$ /opt/SUNWsrspx/bin/srsexec -dvb /etc/shadow OWNED
srsexec: binary_name: OWNED
srsexec: name_buf: OWNED_______________
binaries file line: root:omhyabndnAtNw:6
binaries file line: :6445::::::
Security verification failed for binary: OWNED
see SYSLOG(/var/adm/messages) for errors
Exploitation of this vulnerability allows attackers to gain access to
the root password hash or other sensitive information.
In order to exploit this vulnerability, an attacker must have local user
access to the system.
iDefense has confirmed the existence of this vulnerability in Solaris 10
with the SUNWsrspx package installed. In order to determine if this
package is installed, an administrator can execute the following
# pkginfo SUNWsrspx
If this command returns 'ERROR: information for "SUNWsrspx" was not
found', then the system does not have the affected package installed
and is not vulnerable.
Remove the setuid bit from the srsexec binary:
# chmod -s /opt/SUNWsrspx/bin/srsexec
VI. VENDOR RESPONSE
Sun Microsystems has addressed this vulnerability with a patch release.
For more information, consult Sun Alert ID 102891 at the following URL.
VII. CVE INFORMATION
A Mitre Corp. Common Vulnerabilities and Exposures (CVE) number has not
been assigned yet.
VIII. DISCLOSURE TIMELINE
11/07/2006 Initial vendor notification
11/10/2006 Initial vendor response
05/10/2007 Coordinated public disclosure
The discoverer of this vulnerability wishes to remain anonymous.
Get paid for vulnerability research
Free tools, research and upcoming events
X. LEGAL NOTICES
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 email@example.com 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.