Microsoft Remote Procedure Call (RPC) Server Vulnerability

Posted: 08-11-2003, 08:38 PM
http://www.ciac.org/ciac/bulletins/l-126.shtml

Several people called me, in hysterical panic telling me their computers
restarted, I was on LINUX at the moment and rebooted
to XP to see how I could help them, to my amazment my computer restarted
too!!!

this was an ATTACK!!!! so I disabled the RPC services and I am posting this
for the people who are looking for solutions.

What I did was firewalled XP, and disabled one of the RPC services and made
the other one to not be able to restart the computer.
Then I did an XP update from the windows update site.

Now my ps has not rebooted... I think this is creating GLOBAL chaos!!!

Kenny
www.computerboom.net
www.talentgrid.com




Privacy and Legal Notice

INFORMATION BULLETIN
L-126: Microsoft Remote Procedure Call (RPC) Server Vulnerability
[Microsoft Security Bulletin MS01-041]
July 30, 2001 17:00 GMT
--------------------------------------------------------------------------

PROBLEM: A malformed RPC request can cause a denial of service.
PLATFORM: Those running any of the following products:
a.. Microsoft Exchange Server 5.5
b.. Microsoft Exchange Server 2000
c.. Microsoft SQL Server 7.0
d.. Microsoft SQL Server 2000
e.. Microsoft Windows NT 4.0
f.. Microsoft Windows 2000

DAMAGE: The level of damage could range from minor (e.g., the service
temporarily hanging) to major (e.g., the service failing in a way that would
require the entire system to be restarted).
SOLUTION: Apply the patches and proper firewalling as indicated in the
bulletin.

--------------------------------------------------------------------------

VULNERABILITY
ASSESSMENT: The risk is LOW. Proper firewalling would help minimize
the possibility of attacks by Internet-based users.

--------------------------------------------------------------------------

LINKS:
CIAC BULLETIN: http://www.ciac.org/ciac/bulletins/l-126.shtml

--------------------------------------------------------------------------


[***** Start Microsoft Security Bulletin MS01-041 *****]

- ----------------------------------------------------------------------
Title: Malformed RPC Request Can Cause Service Failure
Date: 26 July 2001
Software: Exchange Server 5.5, Exchange Server 2000,
SQL Server 7.0, SQL Server 2000, Windows NT 4.0,
Windows 2000
Impact: Denial of service
Bulletin: MS01-041


Microsoft encourages customers to review the Security Bulletin at:
http://www.microsoft.com/technet/sec...n/MS01-041.asp
- ----------------------------------------------------------------------


Issue:
======
Several of the RPC servers associated with system services in
Microsoft Exchange, SQL Server, Windows NT 4.0 and Windows 2000 do not
adequately validate inputs, and in some cases will accept invalid
inputs that prevent normal processing. The specific input values at
issue here vary from RPC server to RPC server.

An attacker who sent such inputs to an affected RPC server could
disrupt its service. The precise type of disruption would depend on
the specific service, but could range in effect from minor (e.g., the
service temporarily hanging) to major (e.g., the service failing in a
way that would require the entire system to be restarted).


Mitigating Factors:
====================
- Proper firewalling would help minimize an affected system's
exposure to attack by Internet-based users. In general, a
firewall should block access to all RPC services except
those that are specifically intended for use by untrusted users.


Patch Availability:
===================
- A patch is available to fix this vulnerability. Please read the
Security Bulletin
http://www.microsoft.com/technet/sec...n/ms01-041.asp
for information on obtaining this patch.


Acknowledgment:
===============
- Bindview's Razor Team (http://razor.bindview.com)


- ---------------------------------------------------------------------


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED
"AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL
WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT
SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES
WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL,
LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY
FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY
NOT APPLY.

[***** End Microsoft Security Bulletin MS01-041 *****]


----------------------------------------------------------------------------
----
CIAC wishes to acknowledge the contributions of Microsoft for the
information contained in this bulletin.
----------------------------------------------------------------------------
----
CIAC services are available to DOE, DOE Contractors, and the NIH. CIAC can
be contacted at:
Voice: +1 925-422-8193 (7 x 24)
FAX: +1 925-423-8002
STU-III: +1 925-423-2604
E-mail: ciac@ciac.org
World Wide Web: http://www.ciac.org/
Anonymous FTP: ftp.ciac.org

----------------------------------------------------------------------------
----
This document was prepared as an account of work sponsored by an agency of
the United States Government. Neither the United States Government nor the
University of California nor any of their employees, makes any warranty,
express or implied, or assumes any legal liability or responsibility for the
accuracy, completeness, or usefulness of any information, apparatus,
product, or process disclosed, or represents that its use would not infringe
privately owned rights. Reference herein to any specific commercial
products, process, or service by trade name, trademark, manufacturer, or
otherwise, does not necessarily constitute or imply its endorsement,
recommendation or favoring by the United States Government or the University
of California. The views and opinions of authors expressed herein do not
necessarily state or reflect those of the United States Government or the
University of California, and shall not be used for advertising or product
endorsement purposes.
----------------------------------------------------------------------------
----
UCRL-MI-119788
[Privacy and Legal Notice]


Reply With Quote

Responses to "Microsoft Remote Procedure Call (RPC) Server Vulnerability"

Claude J Ortega
Guest
Posts: n/a
 
Re: Microsoft Remote Procedure Call (RPC) Server Vulnerability
Posted: 08-11-2003, 09:11 PM
In article <en#XuhEYDHA.2648@TK2MSFTNGP09.phx.gbl>, king@hotmail.com says...
> http://www.ciac.org/ciac/bulletins/l-126.shtml
>
> Several people called me, in hysterical panic telling me their computers
> restarted, I was on LINUX at the moment and rebooted
> to XP to see how I could help them, to my amazment my computer restarted
> too!!!
>
> this was an ATTACK!!!! so I disabled the RPC services and I am posting this
> for the people who are looking for solutions.
>
> What I did was firewalled XP, and disabled one of the RPC services and made
> the other one to not be able to restart the computer.
> Then I did an XP update from the windows update site.
>
> Now my ps has not rebooted... I think this is creating GLOBAL chaos!!!
>
> Kenny
> www.computerboom.net
> www.talentgrid.com
>
>
>
>
> Privacy and Legal Notice
>
> INFORMATION BULLETIN
> L-126: Microsoft Remote Procedure Call (RPC) Server Vulnerability
> [Microsoft Security Bulletin MS01-041]
> July 30, 2001 17:00 GMT
> --------------------------------------------------------------------------
>
> PROBLEM: A malformed RPC request can cause a denial of service.
> PLATFORM: Those running any of the following products:
> a.. Microsoft Exchange Server 5.5
> b.. Microsoft Exchange Server 2000
> c.. Microsoft SQL Server 7.0
> d.. Microsoft SQL Server 2000
> e.. Microsoft Windows NT 4.0
> f.. Microsoft Windows 2000
>
> DAMAGE: The level of damage could range from minor (e.g., the service
> temporarily hanging) to major (e.g., the service failing in a way that would
> require the entire system to be restarted).
> SOLUTION: Apply the patches and proper firewalling as indicated in the
> bulletin.
>
> --------------------------------------------------------------------------
>
> VULNERABILITY
> ASSESSMENT: The risk is LOW. Proper firewalling would help minimize
> the possibility of attacks by Internet-based users.
>
> --------------------------------------------------------------------------
>
> LINKS:
> CIAC BULLETIN: http://www.ciac.org/ciac/bulletins/l-126.shtml
>
> --------------------------------------------------------------------------
>
>
> [***** Start Microsoft Security Bulletin MS01-041 *****]
>
> - ----------------------------------------------------------------------
> Title: Malformed RPC Request Can Cause Service Failure
> Date: 26 July 2001
> Software: Exchange Server 5.5, Exchange Server 2000,
> SQL Server 7.0, SQL Server 2000, Windows NT 4.0,
> Windows 2000
> Impact: Denial of service
> Bulletin: MS01-041
>
>
> Microsoft encourages customers to review the Security Bulletin at:
> http://www.microsoft.com/technet/sec...n/MS01-041.asp
> - ----------------------------------------------------------------------
>
>
> Issue:
> ======
> Several of the RPC servers associated with system services in
> Microsoft Exchange, SQL Server, Windows NT 4.0 and Windows 2000 do not
> adequately validate inputs, and in some cases will accept invalid
> inputs that prevent normal processing. The specific input values at
> issue here vary from RPC server to RPC server.
>
> An attacker who sent such inputs to an affected RPC server could
> disrupt its service. The precise type of disruption would depend on
> the specific service, but could range in effect from minor (e.g., the
> service temporarily hanging) to major (e.g., the service failing in a
> way that would require the entire system to be restarted).
>
>
> Mitigating Factors:
> ====================
> - Proper firewalling would help minimize an affected system's
> exposure to attack by Internet-based users. In general, a
> firewall should block access to all RPC services except
> those that are specifically intended for use by untrusted users.
>
>
> Patch Availability:
> ===================
> - A patch is available to fix this vulnerability. Please read the
> Security Bulletin
> http://www.microsoft.com/technet/sec...n/ms01-041.asp
> for information on obtaining this patch.
>
>
> Acknowledgment:
> ===============
> - Bindview's Razor Team (http://razor.bindview.com)
>
>
> - ---------------------------------------------------------------------
>
>
> THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED
> "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL
> WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF
> MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT
> SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES
> WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL,
> LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION
> OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH
> DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY
> FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY
> NOT APPLY.
>
> [***** End Microsoft Security Bulletin MS01-041 *****]
>
>
> ----------------------------------------------------------------------------
> ----
> CIAC wishes to acknowledge the contributions of Microsoft for the
> information contained in this bulletin.
> ----------------------------------------------------------------------------
> ----
> CIAC services are available to DOE, DOE Contractors, and the NIH. CIAC can
> be contacted at:
> Voice: +1 925-422-8193 (7 x 24)
> FAX: +1 925-423-8002
> STU-III: +1 925-423-2604
> E-mail: ciac@ciac.org
> World Wide Web: http://www.ciac.org/
> Anonymous FTP: ftp.ciac.org
>
> ----------------------------------------------------------------------------
> ----
> This document was prepared as an account of work sponsored by an agency of
> the United States Government. Neither the United States Government nor the
> University of California nor any of their employees, makes any warranty,
> express or implied, or assumes any legal liability or responsibility for the
> accuracy, completeness, or usefulness of any information, apparatus,
> product, or process disclosed, or represents that its use would not infringe
> privately owned rights. Reference herein to any specific commercial
> products, process, or service by trade name, trademark, manufacturer, or
> otherwise, does not necessarily constitute or imply its endorsement,
> recommendation or favoring by the United States Government or the University
> of California. The views and opinions of authors expressed herein do not
> necessarily state or reflect those of the United States Government or the
> University of California, and shall not be used for advertising or product
> endorsement purposes.
> ----------------------------------------------------------------------------
> ----
> UCRL-MI-119788
> [Privacy and Legal Notice]
>
>
>
Look at this site for some info about this worm.


http://isc.sans.org/diary.html?date=2003-08-11


--
Claude
Reply With Quote
Cari \(MS-MVP\)
Guest
Posts: n/a
 
Re: Microsoft Remote Procedure Call (RPC) Server Vulnerability
Posted: 08-11-2003, 10:18 PM
http://support.microsoft.com/?kbid=823980

Cari
www.coribright.com

"Claude J Ortega" <cjortega100@hotmail.com> wrote in message
news:MPG.19a1c2694690d9899896d6@news.supernews.com ...
> In article <en#XuhEYDHA.2648@TK2MSFTNGP09.phx.gbl>, king@hotmail.com
says...
> > http://www.ciac.org/ciac/bulletins/l-126.shtml
> >
> > Several people called me, in hysterical panic telling me their computers
> > restarted, I was on LINUX at the moment and rebooted
> > to XP to see how I could help them, to my amazment my computer restarted
> > too!!!
> >
> > this was an ATTACK!!!! so I disabled the RPC services and I am posting
this
> > for the people who are looking for solutions.
> >
> > What I did was firewalled XP, and disabled one of the RPC services and
made
> > the other one to not be able to restart the computer.
> > Then I did an XP update from the windows update site.
> >
> > Now my ps has not rebooted... I think this is creating GLOBAL chaos!!!
> >
> > Kenny
> > www.computerboom.net
> > www.talentgrid.com
> >
> >
> >
> >
> > Privacy and Legal Notice
> >
> > INFORMATION BULLETIN
> > L-126: Microsoft Remote Procedure Call (RPC) Server Vulnerability
> > [Microsoft Security Bulletin MS01-041]
> > July 30, 2001 17:00 GMT
>
> --------------------------------------------------------------------------
> >
> > PROBLEM: A malformed RPC request can cause a denial of service.
> > PLATFORM: Those running any of the following products:
> > a.. Microsoft Exchange Server 5.5
> > b.. Microsoft Exchange Server 2000
> > c.. Microsoft SQL Server 7.0
> > d.. Microsoft SQL Server 2000
> > e.. Microsoft Windows NT 4.0
> > f.. Microsoft Windows 2000
> >
> > DAMAGE: The level of damage could range from minor (e.g., the
service
> > temporarily hanging) to major (e.g., the service failing in a way that
would
> > require the entire system to be restarted).
> > SOLUTION: Apply the patches and proper firewalling as indicated in
the
> > bulletin.
> >
>
> --------------------------------------------------------------------------
> >
> > VULNERABILITY
> > ASSESSMENT: The risk is LOW. Proper firewalling would help
minimize
> > the possibility of attacks by Internet-based users.
> >
>
> --------------------------------------------------------------------------
> >
> > LINKS:
> > CIAC BULLETIN: http://www.ciac.org/ciac/bulletins/l-126.shtml
> >
>
> --------------------------------------------------------------------------
> >
> >
> > [***** Start Microsoft Security Bulletin MS01-041 *****]
> >
> > - ----------------------------------------------------------------------
> > Title: Malformed RPC Request Can Cause Service Failure
> > Date: 26 July 2001
> > Software: Exchange Server 5.5, Exchange Server 2000,
> > SQL Server 7.0, SQL Server 2000, Windows NT 4.0,
> > Windows 2000
> > Impact: Denial of service
> > Bulletin: MS01-041
> >
> >
> > Microsoft encourages customers to review the Security Bulletin at:
> > http://www.microsoft.com/technet/sec...n/MS01-041.asp
> > - ----------------------------------------------------------------------
> >
> >
> > Issue:
> > ======
> > Several of the RPC servers associated with system services in
> > Microsoft Exchange, SQL Server, Windows NT 4.0 and Windows 2000 do not
> > adequately validate inputs, and in some cases will accept invalid
> > inputs that prevent normal processing. The specific input values at
> > issue here vary from RPC server to RPC server.
> >
> > An attacker who sent such inputs to an affected RPC server could
> > disrupt its service. The precise type of disruption would depend on
> > the specific service, but could range in effect from minor (e.g., the
> > service temporarily hanging) to major (e.g., the service failing in a
> > way that would require the entire system to be restarted).
> >
> >
> > Mitigating Factors:
> > ====================
> > - Proper firewalling would help minimize an affected system's
> > exposure to attack by Internet-based users. In general, a
> > firewall should block access to all RPC services except
> > those that are specifically intended for use by untrusted users.
> >
> >
> > Patch Availability:
> > ===================
> > - A patch is available to fix this vulnerability. Please read the
> > Security Bulletin
> > http://www.microsoft.com/technet/sec...n/ms01-041.asp
> > for information on obtaining this patch.
> >
> >
> > Acknowledgment:
> > ===============
> > - Bindview's Razor Team (http://razor.bindview.com)
> >
> >
> > - ---------------------------------------------------------------------
> >
> >
> > THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED
> > "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL
> > WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF
> > MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT
> > SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES
> > WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL,
> > LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT
CORPORATION
> > OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH
> > DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF
LIABILITY
> > FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY
> > NOT APPLY.
> >
> > [***** End Microsoft Security Bulletin MS01-041 *****]
> >
> >
>
> --------------------------------------------------------------------------
--
> > ----
> > CIAC wishes to acknowledge the contributions of Microsoft for the
> > information contained in this bulletin.
>
> --------------------------------------------------------------------------
--
> > ----
> > CIAC services are available to DOE, DOE Contractors, and the NIH. CIAC
can
> > be contacted at:
> > Voice: +1 925-422-8193 (7 x 24)
> > FAX: +1 925-423-8002
> > STU-III: +1 925-423-2604
> > E-mail: ciac@ciac.org
> > World Wide Web: http://www.ciac.org/
> > Anonymous FTP: ftp.ciac.org
> >
>
> --------------------------------------------------------------------------
--
> > ----
> > This document was prepared as an account of work sponsored by an agency
of
> > the United States Government. Neither the United States Government nor
the
> > University of California nor any of their employees, makes any warranty,
> > express or implied, or assumes any legal liability or responsibility for
the
> > accuracy, completeness, or usefulness of any information, apparatus,
> > product, or process disclosed, or represents that its use would not
infringe
> > privately owned rights. Reference herein to any specific commercial
> > products, process, or service by trade name, trademark, manufacturer, or
> > otherwise, does not necessarily constitute or imply its endorsement,
> > recommendation or favoring by the United States Government or the
University
> > of California. The views and opinions of authors expressed herein do not
> > necessarily state or reflect those of the United States Government or
the
> > University of California, and shall not be used for advertising or
product
> > endorsement purposes.
>
> --------------------------------------------------------------------------
--
> > ----
> > UCRL-MI-119788
> > [Privacy and Legal Notice]
> >
> >
> >
>
> Look at this site for some info about this worm.
>
>
> http://isc.sans.org/diary.html?date=2003-08-11
>
>
> --
> Claude

Reply With Quote
Kelly
Guest
Posts: n/a
 
Re: Microsoft Remote Procedure Call (RPC) Server Vulnerability
Posted: 08-12-2003, 07:55 AM
To stop the reboots: Go to Start/Run and type in: services.msc. Scroll down
to Remote Procedure Call (RPC)/Logon/First Failure/Restart the Service.

Then close Windows Explorer, End Process in the Task Manager for
msblast.exe, run the edit on line 257 then run the patch listed below it:
http://www.kellys-korner-xp.com/xp_tweaks.htm

Windows XP Security Patch: Buffer Overrun In RPC Interface Could Allow Code
Execution: http://tinyurl.com/ir5h

More information here:
http://www.kellys-korner-xp.com/xp_qr.htm#rpc


--
All the Best,
Kelly

MS-MVP Win98/XP
[AE-Windows® XP]

Troubleshooting Windows XP
http://www.kellys-korner-xp.com
http://www.kellys-korner-xp.com/xp_abc.htm
http://www.kellys-korner-xp.com/xp_tweaks.htm

Top 10 Frequently Asked Questions and Answers
http://www.kellys-korner-xp.com/top10faqs.htm


"Knight" <king@hotmail.com> wrote in message
news:en%23XuhEYDHA.2648@TK2MSFTNGP09.phx.gbl...
> http://www.ciac.org/ciac/bulletins/l-126.shtml
>
> Several people called me, in hysterical panic telling me their computers
> restarted, I was on LINUX at the moment and rebooted
> to XP to see how I could help them, to my amazment my computer restarted
> too!!!
>
> this was an ATTACK!!!! so I disabled the RPC services and I am posting
this
> for the people who are looking for solutions.
>
> What I did was firewalled XP, and disabled one of the RPC services and
made
> the other one to not be able to restart the computer.
> Then I did an XP update from the windows update site.
>
> Now my ps has not rebooted... I think this is creating GLOBAL chaos!!!
>
> Kenny
> www.computerboom.net
> www.talentgrid.com
>
>
>
>
> Privacy and Legal Notice
>
> INFORMATION BULLETIN
> L-126: Microsoft Remote Procedure Call (RPC) Server Vulnerability
> [Microsoft Security Bulletin MS01-041]
> July 30, 2001 17:00 GMT
> --------------------------------------------------------------------------
>
> PROBLEM: A malformed RPC request can cause a denial of service.
> PLATFORM: Those running any of the following products:
> a.. Microsoft Exchange Server 5.5
> b.. Microsoft Exchange Server 2000
> c.. Microsoft SQL Server 7.0
> d.. Microsoft SQL Server 2000
> e.. Microsoft Windows NT 4.0
> f.. Microsoft Windows 2000
>
> DAMAGE: The level of damage could range from minor (e.g., the
service
> temporarily hanging) to major (e.g., the service failing in a way that
would
> require the entire system to be restarted).
> SOLUTION: Apply the patches and proper firewalling as indicated in
the
> bulletin.
>
> --------------------------------------------------------------------------
>
> VULNERABILITY
> ASSESSMENT: The risk is LOW. Proper firewalling would help minimize
> the possibility of attacks by Internet-based users.
>
> --------------------------------------------------------------------------
>
> LINKS:
> CIAC BULLETIN: http://www.ciac.org/ciac/bulletins/l-126.shtml
>
> --------------------------------------------------------------------------
>
>
> [***** Start Microsoft Security Bulletin MS01-041 *****]
>
> - ----------------------------------------------------------------------
> Title: Malformed RPC Request Can Cause Service Failure
> Date: 26 July 2001
> Software: Exchange Server 5.5, Exchange Server 2000,
> SQL Server 7.0, SQL Server 2000, Windows NT 4.0,
> Windows 2000
> Impact: Denial of service
> Bulletin: MS01-041
>
>
> Microsoft encourages customers to review the Security Bulletin at:
> http://www.microsoft.com/technet/sec...n/MS01-041.asp
> - ----------------------------------------------------------------------
>
>
> Issue:
> ======
> Several of the RPC servers associated with system services in
> Microsoft Exchange, SQL Server, Windows NT 4.0 and Windows 2000 do not
> adequately validate inputs, and in some cases will accept invalid
> inputs that prevent normal processing. The specific input values at
> issue here vary from RPC server to RPC server.
>
> An attacker who sent such inputs to an affected RPC server could
> disrupt its service. The precise type of disruption would depend on
> the specific service, but could range in effect from minor (e.g., the
> service temporarily hanging) to major (e.g., the service failing in a
> way that would require the entire system to be restarted).
>
>
> Mitigating Factors:
> ====================
> - Proper firewalling would help minimize an affected system's
> exposure to attack by Internet-based users. In general, a
> firewall should block access to all RPC services except
> those that are specifically intended for use by untrusted users.
>
>
> Patch Availability:
> ===================
> - A patch is available to fix this vulnerability. Please read the
> Security Bulletin
> http://www.microsoft.com/technet/sec...n/ms01-041.asp
> for information on obtaining this patch.
>
>
> Acknowledgment:
> ===============
> - Bindview's Razor Team (http://razor.bindview.com)
>
>
> - ---------------------------------------------------------------------
>
>
> THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED
> "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL
> WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF
> MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT
> SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES
> WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL,
> LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION
> OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH
> DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY
> FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY
> NOT APPLY.
>
> [***** End Microsoft Security Bulletin MS01-041 *****]
>
>
> --------------------------------------------------------------------------
--
> ----
> CIAC wishes to acknowledge the contributions of Microsoft for the
> information contained in this bulletin.
> --------------------------------------------------------------------------
--
> ----
> CIAC services are available to DOE, DOE Contractors, and the NIH. CIAC can
> be contacted at:
> Voice: +1 925-422-8193 (7 x 24)
> FAX: +1 925-423-8002
> STU-III: +1 925-423-2604
> E-mail: ciac@ciac.org
> World Wide Web: http://www.ciac.org/
> Anonymous FTP: ftp.ciac.org
>
> --------------------------------------------------------------------------
--
> ----
> This document was prepared as an account of work sponsored by an agency of
> the United States Government. Neither the United States Government nor the
> University of California nor any of their employees, makes any warranty,
> express or implied, or assumes any legal liability or responsibility for
the
> accuracy, completeness, or usefulness of any information, apparatus,
> product, or process disclosed, or represents that its use would not
infringe
> privately owned rights. Reference herein to any specific commercial
> products, process, or service by trade name, trademark, manufacturer, or
> otherwise, does not necessarily constitute or imply its endorsement,
> recommendation or favoring by the United States Government or the
University
> of California. The views and opinions of authors expressed herein do not
> necessarily state or reflect those of the United States Government or the
> University of California, and shall not be used for advertising or product
> endorsement purposes.
> --------------------------------------------------------------------------
--
> ----
> UCRL-MI-119788
> [Privacy and Legal Notice]
>
>
Reply With Quote
 
LinkBack Thread Tools Display Modes
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
Remote Procedure Call Matt Windows XP Help & Support 102 02-26-2004 07:52 PM
Remote Procedure Call (RPC) patchrb Windows XP Performance & Maintenance 7 11-06-2003 06:13 AM
The Remote Procedure Call (RPC) Jupiter Jones [MVP] Windows XP Work Remotely 0 09-05-2003 11:06 PM
Remote Procedure Call Bob Benson Windows XP Accessibility 5 08-24-2003 06:26 AM
remote call procedure call failed Dave Warwick Windows XP Network & Web 0 07-05-2003 03:59 AM