Check Point Advisories

Microsoft Windows SMB Client Pool Corruption (MS10-006; CVE-2010-0016)

Check Point Reference: CPAI-2010-002
Date Published: 9 Feb 2010
Severity: Critical
Last Updated: Tuesday 09 February, 2010
Source:
Industry Reference:CVE-2010-0016
Protection Provided by:

Security Gateway
R81, R80, R77, R75, R71, R70, R65

Who is Vulnerable?
Vulnerability Description The SMB Protocol is a network file sharing protocol that is implemented in Microsoft Windows. A remote code execution vulnerability has been reported in the Microsoft Server Message Block (SMB) Protocol. The vulnerability is due to an error in the Microsoft SMB implementation that improperly validates fields in the SMB response. A remote attacker could exploit this flaw by hosting a malicious SMB server that is designed to exploit this vulnerability and then convince a user to initiate an SMB connection with it. Successful exploitation could lead to a pool corruption that may allow execution of arbitrary code on the target system. Security Gateway: R70 VPN-1 Power/UTM: NGX R65 VPN-1 Power VSX: NGX R65

Protection Overview

This protection will detect and block attempts to exploit this vulnerability

In order for the protection to be activated, update your Security Gateway product to the latest IPS update. For information on how to update IPS, go to SBP-2006-05, click on Protection tab and select the version of your choice.

Security Gateway R80 / R77 / R75 / R71 / R70 / R65

  1. In the IPS tab, click Protections and find the Microsoft Windows SMB Client Pool Corruption (MS10-006) protection using the Search tool and Edit the protection's settings.
  2. Install policy on all Security Gateways.

This protection's log will contain the following information:

Attack Name:  Windows SMB Protection Violation.
Attack Information:  Microsoft Windows SMB client pool corruption (MS10-006)

×
  Feedback
This website uses cookies for its functionality and for analytics and marketing purposes. By continuing to use this website, you agree to the use of cookies. For more information, please read our Cookies Notice.
OK