Lucene search

K
certCERTVU:575892
HistoryOct 16, 2003 - 12:00 a.m.

Buffer overflow in Microsoft Messenger Service

2003-10-1600:00:00
www.kb.cert.org
26

7.5 High

CVSS2

Access Vector

NETWORK

Access Complexity

LOW

Authentication

NONE

Confidentiality Impact

PARTIAL

Integrity Impact

PARTIAL

Availability Impact

PARTIAL

AV:N/AC:L/Au:N/C:P/I:P/A:P

0.971 High

EPSS

Percentile

99.8%

Overview

There is a buffer overflow in the Microsoft Windows Messenger service that could allow an attacker to execute arbitrary code on most recent versions of Microsoft Windows.

Description

There is a buffer overflow vulnerability in the Microsoft Windows Messenger service. This could allow an attacker to execute arbitrary code with System privileges. Microsoft recommends immediately disabling the Messenger service and evaluating the need for the patch. For more information, see Microsoft Security Bulletin MS03-043. This vulnerability affects virtually all recent versions of Windows with the exception of Microsoft Windows Millennium Edition. On Windows Server 2003, the Messenger service is disabled by default; however, if it is enabled the server is vulnerable to compromise.


Impact

An attacker can run arbitrary code with Local System privileges.


Solution

Disable the Windows messenger service and evaluate the need to apply the patch. to disable the Messenger service, follow these steps as provided by Microsoft:

  1. _Click _Start _, and then click _Control Panel _(or point to _Settings _, and then click _Control Panel _). _
  2. Double-click _Administrative Tools _.
  3. Double-click _Services _.
  4. Double-click _Messenger _.
  5. _In the __Startup type _list, click _Disabled _.
  6. Click _Stop _, and then click _OK _.

_Impact of Workaround: __If the Messenger service is disabled, messages from the Alerter service (for example notifications from your backup software or Uninterruptible Power Supply) are not transmitted. If the Messenger service is disabled, any services that explicitly depend on the Messenger service do not start, and an error message is logged in the System event log. _

The image below illustrates this procedure on Microsoft Windows XP. It will appear different on different versions of Windows.

You should carefully consider the impact of disabling the Messenger service.

As a general rule, and as a partial workaround to this problem, block ports 137 through 139 and UDP broadcast packets at your network perimeter and/or at the host level. This will limit the ability of external attackers to reach vulnerable systems.


Vendor Information

575892

Filter by status: All Affected Not Affected Unknown

Filter by content: __ Additional information available

__ Sort by: Status Alphabetical

Expand all

Javascript is disabled. Click here to view vendors.

Microsoft Corporation __ Affected

Updated: October 15, 2003

Status

Affected

Vendor Statement

We have not received a statement from the vendor.

Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.

Addendum

See Microsoft Security Bulletin MS03-043.

If you have feedback, comments, or additional information about this vulnerability, please send us [email](<mailto:[email protected]?Subject=VU%23575892 Feedback>).

CVSS Metrics

Group Score Vector
Base
Temporal
Environmental

References

Acknowledgements

Our thanks to Microsoft for the information contained in their bulletin. Microsoft has credited the Last Stage of Delirium Research Group for discovering the vulnerability.

This document was written by Shawn Hernan, based on information provided by Microsoft. .

Other Information

CVE IDs: CVE-2003-0717
Severity Metric: 50.63 Date Public:

7.5 High

CVSS2

Access Vector

NETWORK

Access Complexity

LOW

Authentication

NONE

Confidentiality Impact

PARTIAL

Integrity Impact

PARTIAL

Availability Impact

PARTIAL

AV:N/AC:L/Au:N/C:P/I:P/A:P

0.971 High

EPSS

Percentile

99.8%