lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <472F4CCB.1080200@idefense.com>
Date: Mon, 05 Nov 2007 12:03:07 -0500
From: iDefense Labs <labs-no-reply@...fense.com>
To: vulnwatch@...nwatch.org, full-disclosure@...ts.grok.org.uk,
	bugtraq@...urityfocus.com
Subject: iDefense Security Advisory 11.02.07: Sun Microsystems Solaris srsexec
 Format String Vulnerability

iDefense Security Advisory 11.02.07
http://labs.idefense.com/intelligence/vulnerabilities/
Nov 02, 2007

I. BACKGROUND

The srsexec utility is part of the SRS Proxy Core package that is
available with Solaris 10. This package is used to monitor the
performance of clients running Solaris from a centralized
administrative console. This software would be installed on all of the
client machines being monitored and is set-uid root by default. More
information is available at the vendor's site.

http://www.sun.com/service/netconnect/

II. DESCRIPTION

Local exploitation of a format string vulnerability in the srsexec
binary, optionally included in Sun Microsystems Inc.'s Solaris 10,
allows attackers to execute arbitrary code with root privileges.

The vulnerability exists since attacker supplied data is passed directly
to the syslog() function as the format string. This allows an attacker
to overwrite arbitrary memory with arbitrary data, and can result in
the execution of arbitrary code with root privileges.

III. ANALYSIS

Exploitation results in the execution of arbitrary code with root
privileges. In order to exploit this vulnerability, an attacker must
have the ability to execute the set-uid root binary.

The SRS Proxy Core package is not installed by default, but it is a
common application.

IV. DETECTION

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
command:

  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.

V. WORKAROUND

To prevent exploitation of this vulnerability, remove the set-uid bit
from the srsexec binary as shown below.

  # chmod -s /opt/SUNWsrspx/bin/srsexec

VI. VENDOR RESPONSE

Sun Microsystems has addressed this vulnerability by releasing patches.
For more information, consult Sun Alert 103119 at the following URL.

http://sunsolve.sun.com/search/document.do?assetkey=1-26-103119-1

VII. CVE INFORMATION

The Common Vulnerabilities and Exposures (CVE) project has assigned the
name CVE-2007-3880 to this issue. This is a candidate for inclusion in
the CVE list (http://cve.mitre.org/), which standardizes names for
security problems.

VIII. DISCLOSURE TIMELINE

07/18/2007  Initial vendor notification
07/18/2007  Initial vendor response
11/02/2007  Public disclosure

IX. CREDIT

This vulnerability was discovered by Sean Larsson of VeriSign iDefense
Labs.

Get paid for vulnerability research
http://labs.idefense.com/methodology/vulnerability/vcp.php

Free tools, research and upcoming events
http://labs.idefense.com/

X. LEGAL NOTICES

Copyright © 2007 iDefense, 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 customerservice@...fense.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.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ