Вы находитесь на странице: 1из 3

======================================================================= title: Symlink Following and Second-Order Symlink Vulnerabilities in Multiple Check Point Security Management Products product:

Check Point Security Management * Multi-Domain Security Management / Provider-1 * SmartCenter vulnerable version: multiple products, see sections below fixed version: multiple products, see sections below CVE number: CVE-2011-2664 impact: high homepage: http://www.checkpoint.com found: 2010-08-13 by: Matthew Flanagan http://wadofstuff.blogspot.com ======================================================================= Vendor Product Description -------------------------"Security Management and Multi-Domain Security Management (Provider-1) delivers more security and control by segmenting your security management into multiple virtual domains. Businesses of all sizes can easily create virtual domains based on geography, business unit or security function to strengthen security and simplify management." URL: http://www.checkpoint.com/products/multi-domain-security-management/index.h tml "Check Point UTM-1 Edge appliances deliver proven, best-in-class security right out of the box! These simple, all-in-one appliances allow branch offices to deploy comprehensive security quickly and easily. These appliances offer robust performance, powerful central management and advanced wireless options." URL: http://www.checkpoint.com/products/utm-1-edge/index.html Vulnerability Description ------------------------A post-installation shell script is executed both in the provisioning of a Security Management Domain and installation of a standalone SmartCenter. The script is used to generate a configuration file for use by the SofaWare Management Server (SMS). The SMS is used to send all configuration changes performed in the SmartCenter/Management Domain to UTM-1 Edge devices. UTM-1 Edge devices also communicate their status to the SmartCenter/Management Domain via SMS. Due to the combination of inadequate file checks, predictable file names and writing of temporary configuration files to /tmp it is possible for a unprivileged local user to exploit the post-installation script to overwrite arbitrary files on the security management system through symlink following. The script also contains a second-order symlink vulnerability [1] which makes it possible for an attacker to gain control of the SMS configuration file: $FWDIR/conf/sofaware/SWManagementServer.ini. The SWManagementServer.ini file contains sensitive information and configuration parameters for the management of UTM-1 Edge firewall appliances such as firmware versions, mail proxies, logging levels, and many timeout and polling intervals for various software components running on the Edge devices.

The likelhood of exploiting this vulnerability on a server running SmartCenter is low due to it only being exploitable during the installation of the software. However, for Management Domains running on a Multi-Domain Management / Provider-1 server the likelihood is much higher as the vulnerability can be exploited every time a new Management Domain is created. Exploit ------An exploit will not be published. Vulnerable Versions ------------------R65.70 R70.40 R71.30 R75.10 On Linux, SecurePlatform and Solaris. Solution -------Fixed in R71.40 and R75.20. Other versions can get fix from Check Point advisory page: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewso lutiondetails=&solutionid=syyk63565 Advisories ---------https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewso lutiondetails=&solutionid=syyk63565 http://wadofstuff.blogspot.com/2011/08/security-advisory-symlink-following-and.h tml Vendor Contact Timeline ----------------------2010-08-16: Contacted Check Point security team security-alert () checkpoint.com. 2010-08-16: Vendor responded. 2010-08-16: Provided vulnerability details and exploit to vendor. 2010-08-18: Vendor confirmation of vulnerability. 2010-08-26: Requested a status update from the vendor. 2010-08-28: Vendor: working on a fix and release plan. 2011-05-31: Requested a status update from the vendor. 2011-06-01: Vendor: Fixed in R75. Advisory to be released on 2011-06-15. 2011-06-06: Advised vendor that R75 GA and R75.10 are still vulnerable. 2011-06-06: Applied for CVE number from MITRE. 2011-06-07 - 2011-06-14: Coordinated fix and advisory release with Check Point. 2011-06-14: Sent more details to MITRE. 2011-06-15: Vendor publishes advisory and fix. 2011-06-16: Contacted AusCERT. 2011-07-06: Asked MITRE for status of CVE number allocation. 2011-07-07: Assigned CVE number by MITRE. 2011-08-16: Released advisory.

References ---------[1] http://www.securityfocus.com/archive/1/401682