[NT] Microsoft Routing and Remote Access Code Execution Vulnerabilities (MS06-025)
- From: SecuriTeam <support@xxxxxxxxxxxxxx>
- Date: 14 Jun 2006 12:29:57 +0200
The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com
- - promotion
The SecuriTeam alerts list - Free, Accurate, Independent.
Get your security news from a reliable source.
http://www.securiteam.com/mailinglist.html
- - - - - - - - -
Microsoft Routing and Remote Access Code Execution Vulnerabilities
(MS06-025)
------------------------------------------------------------------------
SUMMARY
There is a remote code execution vulnerability in the Routing and Remote
Access Service that could allow an attacker who successfully exploited
this vulnerability to take complete control of the affected system. There
is a remote code execution vulnerability in the Routing and Remote Access
Service that could allow an attacker who successfully exploited this
vulnerability to take complete control of the affected system.
A vulnerability in Routing and Remote Access Could Allow Remote Code
Execution.
DETAILS
Vulnerable Systems:
* Microsoft Windows 2000 Service Pack 4 -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=c1af96b2-2807-444b-82df-b6b61ec63715> Download the update
* Microsoft Windows XP Service Pack 1 and Microsoft Windows XP Service
Pack 2 -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=74838e2b-bd5f-4584-81f1-3250e6b69728> Download the update
* Microsoft Windows XP Professional x64 Edition -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=09d1a284-6a16-44a5-a95e-8eb566401ce9> Download the update
* Microsoft Windows Server 2003 and Microsoft Windows Server 2003 Service
Pack 1 -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=b4264cb9-8979-40e8-b903-bc8deda00fec> Download the update
* Microsoft Windows Server 2003 for Itanium-based Systems and Microsoft
Windows Server 2003 with SP1 for Itanium-based Systems -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=890535c9-98cf-49a9-ae50-178e3c5fac6b> Download the update
* Microsoft Windows Server 2003 x64 Edition -
<http://www.microsoft.com/downloads/details.aspx?FamilyId=bf9cef95-89fd-4ec3-be0a-93902f2bb768> Download the update
Immune Systems:
* Microsoft Windows 98, Microsoft Windows 98 Second Edition (SE), and
Microsoft Windows Millennium Edition (Me)
Note The security updates for Microsoft Windows Server 2003, Windows
Server 2003 Service Pack 1, and Windows Server 2003 x64 Edition also apply
to Windows Server 2003 R2.
RRAS Memory Corruption Vulnerability - CVE-2006-2370:
There is a remote code execution vulnerability in the Routing and Remote
Access Service that could allow an attacker who successfully exploited
this vulnerability to take complete control of the affected system.
Mitigating factors for RRAS Memory Corruption Vulnerability -
CVE-2006-2370:
* The Remote Access Connection Manager service is not started by default
for all supported Microsoft Windows operating systems with the exception
of Microsoft Windows 2000 Service Pack 4. The only service dependent upon
the Remote Access Connection Manager service is the Remote Access Auto
Connection Manager. For Microsoft Windows 2000, the Internet Connection
Sharing service depends on the Remote Access Connection Manager service.
Enabling a dependent service could cause the Remote Access Connection
Manager service to start.
* On Windows XP Service Pack 2 and Windows Server 2003 systems, an
attacker must have valid logon credentials and be able to log on locally
to exploit this vulnerability. The vulnerability could not be exploited
remotely by anonymous users or by users who have standard user accounts.
However, the affected component is available remotely to users who have
administrative permissions.
* Firewall best practices and standard default firewall configurations
can help protect networks from attacks that originate outside the
enterprise perimeter. Best practices recommend that systems that are
connected to the Internet have a minimal number of ports exposed.
Workarounds for RRAS Memory Corruption Vulnerability- CVE-2006-2370:
Microsoft has tested the following workarounds. Although these workarounds
will not correct the underlying vulnerability, they help block known
attack vectors. When a workaround reduces functionality, it is identified
in the following section.
* Disable the Remote Access Connection Manager service
Disabling the Remote Access Connection Manager service will help protect
the affected system from attempts to exploit this vulnerability. To
disable the Routing and Remote Access service, follow these steps:
1. Click Start, and then click Control Panel. Alternatively, point to
Settings, and then click Control Panel.
2. Double-click Administrative Tools.
3. Double-click Services.
4. Double-click Remote Access Connection Manager
5. In the Startup type list, click Disabled.
6. Click Stop, and then click OK.
You can also stop and disable the Routing and Remote Access service by
using the following command at the command prompt:
sc stop rasman & sc config rasman start= disabled
Impact of Workaround: If you disable the Remote Access Connection Manager
service, you cannot offer routing services to other hosts in local area
and wide area network environments. Therefore, we recommend this
workaround only on systems that do not require the use of RASMAN for
remote access and routing.
* Block the following at the firewall:
* UDP ports 135, 137, 138, and 445, and TCP ports 135, 139, 445, and
593
* All unsolicited inbound traffic on ports greater than 1024
* Any other specifically configured RPC port
These ports are used to initiate a connection with RPC. Blocking them at
the firewall will help protect systems that are behind that firewall from
attempts to exploit this vulnerability. Also, make sure that you block any
other specifically configured RPC port on the remote system. We recommend
that you block all unsolicited inbound communication from the Internet to
help prevent attacks that may use other ports. For more information about
ports that RPC uses, visit the following
<http://go.microsoft.com/fwlink/?LinkId=21312> Web site.
* To help protect from network-based attempts to exploit this
vulnerability, use a personal firewall, such as the
<http://go.microsoft.com/fwlink/?LinkId=33335> Internet Connection
Firewall, which is included with Windows XP and with Windows Server 2003.
By default, the Internet Connection Firewall feature in Windows XP and in
Windows Server 2003 helps protect your Internet connection by blocking
unsolicited incoming traffic. We recommend that you block all unsolicited
incoming communication from the Internet. In Windows XP Service Pack 2
this features is called the Windows Firewall.
To enable the Internet Connection Firewall feature by using the Network
Setup Wizard, follow these steps:
1. Click Start, and then click Control Panel.
2. In the default Category View, click Network and Internet Connections,
and then click Setup or change your home or small office network. The
Internet Connection Firewall feature is enabled when you select a
configuration in the Network Setup Wizard that indicates that your system
is connected directly to the Internet.
To configure Internet Connection Firewall manually for a connection,
follow these steps:
1. Click Start, and then click Control Panel.
2. In the default Category View, click Networking and Internet
Connections, and then click Network Connections.
3. Right-click the connection on which you want to enable Internet
Connection Firewall, and then click Properties.
4. Click the Advanced tab.
5. Click to select the Protect my computer or network by limiting or
preventing access to this computer from the Internet check box, and then
click OK.
Note If you want to enable certain programs and services to communicate
through the firewall, click Settings on the Advanced tab, and then select
the programs, the protocols, and the services that are required.
* To help protect from network-based attempts to exploit this
vulnerability, enable advanced TCP/IP filtering on systems that support
this feature.
You can enable advanced TCP/IP filtering to block all unsolicited inbound
traffic. For more information about how to configure TCP/IP filtering, see
<http://support.microsoft.com/kb/309798> Microsoft Knowledge Base Article
309798.
* To help protect from network-based attempts to exploit this
vulnerability, block the affected ports by using IPSec on the affected
systems.
Use Internet Protocol security (IPSec) to help protect network
communications. Detailed information about IPSec and about how to apply
filters is available in <http://support.microsoft.com/kb/313190>
Microsoft Knowledge Base Article 313190 and
<http://support.microsoft.com/kb/813878> Microsoft Knowledge Base Article
813878
FAQ for RRAS Memory Corruption Vulnerability - CVE-2006-2370:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who
successfully exploited this vulnerability could remotely take complete
control of an affected system. An attacker could then install programs;
view, change, or delete data; or create new accounts with full user
rights.
What causes the vulnerability?
An unchecked buffer in the Routing and Remote Access service.
What are RRAS and RAS?
RRAS makes it possible for a computer to function as a network router.
RRAS also provides the next generation of server functionality for the
Remote Access Service (RAS) for Windows. The RRAS server functionality
follows and builds upon the Remote Access Service (RAS) that was included
in previous operating systems
The Remote Access Service lets users connect to a remote computer over
phone lines, so they can work as if their system were physically connected
to the remote network. These services enable remote users to do activities
such as send and receive e-mail, fax documents, retrieve files, and print
documents on an office printer.
The Remote Access Service is a native service in Windows 2000, Windows XP
and Windows Server 2003.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take
complete control of the affected system.
Who could exploit the vulnerability?
On Windows 2000 Service Pack 4 and Windows XP Service Pack 1, any
anonymous user who could deliver a specially crafted message to the
affected system could try to exploit this vulnerability. In order to
exploit the vulnerability on Windows XP Service Pack 2 and Windows Server
2003, an attacker must have valid login credentials to a target system.
How could an attacker exploit the vulnerability?
An attacker could also access the affected component through another
vector. For example, an attacker could log on to the system interactively
or by using another program that passes parameters to the vulnerable
component either locally or remotely.
What systems are primarily at risk from the vulnerability?
Microsoft Windows 2000, Windows XP and Windows Server 2003 are primarily
at risk from this vulnerability. Systems that use Internet Connection
Sharing are also at risk as RRAS must be enabled for ICS functionality.
Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition
critically affected by this vulnerability?
No. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition
do not contain the affected component.
Could the vulnerability be exploited over the Internet?
An attacker could try to exploit this vulnerability over the Internet.
Firewall best practices and standard default firewall configurations can
help protect against attacks that originate from the Internet. Microsoft
has provided information about how you can help protect your PC. End users
can visit the <http://go.microsoft.com/fwlink/?LinkId=21169> Protect Your
PC Web site. IT professionals can visit the
<http://go.microsoft.com/fwlink/?LinkId=21171> Security Guidance Center
Web site.
What does the update do?
The update removes the vulnerability by validating the way that Routing
and Remote Access handles RPC related requests.
When this security bulletin was issued, had this vulnerability been
publicly disclosed?
No. Microsoft received information about this vulnerability through
responsible disclosure. Microsoft had not received any information to
indicate that this vulnerability had been publicly disclosed when this
security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports
that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this
vulnerability had been publicly used to attack customers and had not seen
any examples of proof of concept code published when this security
bulletin was originally issued.
RASMAN Registry Corruption Vulnerability - CVE-2006-2371:
There is a remote code execution vulnerability in the Routing and Remote
Access Service that could allow an attacker who successfully exploited
this vulnerability to take complete control of the affected system.
Mitigating Factors for RASMAN Registry Corruption Vulnerability -
CVE-2006-2371:
* The Remote Access Connection Manager service is not started by default
for all supported Microsoft Windows operating systems with the exception
of Microsoft Windows 2000 Service Pack 4. The only service dependent upon
the Remote Access Connection Manager service is the Remote Access Auto
Connection Manager. For Microsoft Windows 2000, the Internet Connection
Sharing service depends on the Remote Access Connection Manager service.
Enabling a dependent service could cause the Remote Access Connection
Manager service to start.
* On Windows XP SERVICE PACK 2 and Windows Server 2003 systems, an
attacker must have valid logon credentials and be able to log on locally
to exploit this vulnerability. The vulnerability could not be exploited
remotely by anonymous users or by users who have standard user accounts.
However, the affected component is available remotely to users who have
administrative permissions
* Firewall best practices and standard default firewall configurations
can help protect networks from attacks that originate outside the
enterprise perimeter. Best practices recommend that systems that are
connected to the Internet have a minimal number of ports exposed.
Workarounds for RASMAN Registry Corruption Vulnerability - CVE-2006-2371:
Microsoft has tested the following workarounds. Although these workarounds
will not correct the underlying vulnerability, they help block known
attack vectors. When a workaround reduces functionality, it is identified
in the following section.
* Disable the Remote Access Connection Manager service.
Disabling the Remote Access Connection Manager service will help protect
the affected system from attempts to exploit this vulnerability. To
disable the Routing and Remote Access service, follow these steps:
1. Click Start, and then click Control Panel. Alternatively, point to
Settings, and then click Control Panel.
2. Double-click Administrative Tools.
3. Double-click Services.
4. Double-click Remote Access Connection Manager
5. In the Startup type list, click Disabled.
6. Click Stop, and then click OK.
You can also stop and disable the Remote Access Connection Manager service
by using the following command at the command prompt:
sc stop rasman & sc config rasman start= disabled
* To help protect from network-based attempts to exploit this
vulnerability, use a personal firewall, such as the Internet Connection
Firewall, which is included with Windows XP and with Windows Server 2003.
By default, the Internet Connection Firewall feature in Windows XP and in
Windows Server 2003 helps protect your Internet connection by blocking
unsolicited incoming traffic. We recommend that you block all unsolicited
incoming communication from the Internet. In Windows XP Service Pack 2
this features is called the Windows Firewall.
To enable the Internet Connection Firewall feature by using the Network
Setup Wizard, follow these steps:
1. Click Start, and then click Control Panel.
2. In the default Category View, click Network and Internet Connections,
and then click Setup or change your home or small office network. The
Internet Connection Firewall feature is enabled when you select a
configuration in the Network Setup Wizard that indicates that your system
is connected directly to the Internet.
To configure Internet Connection Firewall manually for a connection,
follow these steps:
1. Click Start, and then click Control Panel.
2. In the default Category View, click Networking and Internet
Connections, and then click Network Connections.
3. Right-click the connection on which you want to enable Internet
Connection Firewall, and then click Properties.
4. Click the Advanced tab.
5. Click to select the Protect my computer or network by limiting or
preventing access to this computer from the Internet check box, and then
click OK.
Note If you want to enable certain programs and services to communicate
through the firewall, click Settings on the Advanced tab, and then select
the programs, the protocols, and the services that are required.
* To help protect from network-based attempts to exploit this
vulnerability, enable advanced TCP/IP filtering on systems that support
this feature.
You can enable advanced TCP/IP filtering to block all unsolicited inbound
traffic. For more information about how to configure TCP/IP filtering, see
<http://support.microsoft.com/kb/309798> Microsoft Knowledge Base Article
309798.
* To help protect from network-based attempts to exploit this
vulnerability, block the affected ports by using IPSec on the affected
systems.
Use Internet Protocol security (IPSec) to help protect network
communications. Detailed information about IPSec and about how to apply
filters is available in <http://support.microsoft.com/kb/313190>
Microsoft Knowledge Base Article 313190 and
<http://support.microsoft.com/kb/813878> Microsoft Knowledge Base Article
813878.
Impact of Workaround: If you disable the Routing and Remote Access
service, you cannot offer routing services to other hosts in local area
and wide area network environments. Therefore, we recommend this
workaround only on systems that do not require the use of RRAS for remote
access and routing.
* Block the following at the firewall:
* UDP ports 135, 137, 138, and 445, and TCP ports 135, 139, 445, and
593
* All unsolicited inbound traffic on ports greater than 1024
* Any other specifically configured RPC port
These ports are used to initiate a connection with RPC. Blocking them at
the firewall will help protect systems that are behind that firewall from
attempts to exploit this vulnerability. Also, make sure that you block any
other specifically configured RPC port on the remote system. We recommend
that you block all unsolicited inbound communication from the Internet to
help prevent attacks that may use other ports. For more information about
ports that RPC uses, visit the following Web site
FAQ for RASMAN Registry Corruption Vulnerability - CVE-2006-2371:
What is the scope of the vulnerability?
This is a remote code execution vulnerability. An attacker who
successfully exploited this vulnerability could remotely take complete
control of an affected system. An attacker could then install programs;
view, change, or delete data; or create new accounts with full user
rights.
What causes the vulnerability?
An unchecked buffer in the Routing and Remote Access service.
What are RRAS and RAS?
RRAS makes it possible for a computer to function as a network router.
RRAS also provides the next generation of server functionality for the
Remote Access Service (RAS) for Windows. The RRAS server functionality
follows and builds upon the Remote Access Service (RAS) that was included
in previous operating systems.
The Remote Access Service lets users connect to a remote computer over
phone lines, so they can work as if their system were physically connected
to the remote network. These services enable remote users to do activities
such as send and receive e-mail, fax documents, retrieve files, and print
documents on an office printer.
The Remote Access Service is a native service in Windows 2000, Windows XP
and Windows Server 2003.
What might an attacker use the vulnerability to do?
An attacker who successfully exploited this vulnerability could take
complete control of the affected system.
Who could exploit the vulnerability?
On Windows 2000 Service Pack 4 and Windows XP Service Pack 1, any
anonymous user who could deliver a specially crafted message to the
affected system could try to exploit this vulnerability. In order to
exploit the vulnerability on Windows XP Service Pack 2 and Windows Server
2003, an attacker must have valid login credentials to a target system.
How could an attacker exploit the vulnerability?
An attacker could also access the affected component through another
vector. For example, an attacker could log on to the system interactively
or by using another program that passes parameters to the vulnerable
component either locally or remotely.
What systems are primarily at risk from the vulnerability?
Microsoft Windows 2000, Windows XP and Windows Server 2003 are primarily
at risk from this vulnerability. Systems that use Internet Connection
Sharing are also at risk as RRAS must be enabled for ICS functionality.
Are Windows 98, Windows 98 Second Edition or Windows Millennium Edition
critically affected by this vulnerability?
No. Windows 98, Windows 98 Second Edition, and Windows Millennium Edition
do not contain the affected component.
Could the vulnerability be exploited over the Internet?
An attacker could try to exploit this vulnerability over the Internet.
Firewall best practices and standard default firewall configurations can
help protect against attacks that originate from the Internet. Microsoft
has provided information about how you can help protect your PC. End users
can visit the <http://go.microsoft.com/fwlink/?LinkId=21169> Protect Your
PC Web site. IT professionals can visit the
<http://go.microsoft.com/fwlink/?LinkId=21171> Security Guidance Center
Web site.
What does the update do?
The update removes the vulnerability by validating the way that Routing
and Remote Access handles RPC related requests.
When this security bulletin was issued, had this vulnerability been
publicly disclosed?
No. Microsoft received information about this vulnerability through
responsible disclosure. Microsoft had not received any information to
indicate that this vulnerability had been publicly disclosed when this
security bulletin was originally issued.
When this security bulletin was issued, had Microsoft received any reports
that this vulnerability was being exploited?
No. Microsoft had not received any information to indicate that this
vulnerability had been publicly used to attack customers and had not seen
any examples of proof of concept code published when this security
bulletin was originally issued.
ADDITIONAL INFORMATION
The information has been provided by Microsoft Security.
The original article can be found at:
<http://www.microsoft.com/technet/security/bulletin/ms06-025.mspx>
http://www.microsoft.com/technet/security/bulletin/ms06-025.mspx
========================================
This bulletin is sent to members of the SecuriTeam mailing list.
To unsubscribe from the list, send mail with an empty subject line and body to: list-unsubscribe@xxxxxxxxxxxxxx
In order to subscribe to the mailing list, simply forward this email to: list-subscribe@xxxxxxxxxxxxxx
====================
====================
DISCLAIMER:
The information in this bulletin is provided "AS IS" without warranty of any kind.
In no event shall we be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages.
- Prev by Date: [NT] RPC Mutual Authentication Spoofing (MS06-031)
- Next by Date: [NT] Microsoft PowerPoint Remote Code Execution (MS06-028)
- Previous by thread: [NT] RPC Mutual Authentication Spoofing (MS06-031)
- Next by thread: [NT] Microsoft PowerPoint Remote Code Execution (MS06-028)
- Index(es):
Relevant Pages
|
|
